Locating a person of interest using shared video footage from audio/video recording and communication devices

ABSTRACT

Systems and methods for communicating in a network using share signals in accordance with various embodiments of the present disclosure are provided. In one embodiment, a method for sharing video footage captured by audio/video (A/V) recording and communication devices is provided, the method comprising: receiving from a first client device a share signal including first image data including a person of interest; receiving from a second A/V recording and communication device second image data; transmitting to a second client device, the first image data and a request to check the second image data; receiving from the second client device a locate person command signal; searching the second image data for a match of the person of interest; and when a match of the person of interest is found, generating and transmitting an alert signal that includes a notification that the person of interest was matched in the second image data.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. application Ser. No.15/480,214, filed on Apr. 5, 2017, which is a continuation-in-part ofU.S. application Ser. No. 15/431,607, filed on Feb. 13, 2017, and U.S.application Ser. No. 15/431,275, filed on Feb. 13, 2017, each of whichclaims priority to provisional application Ser. No. 62/376,826, filed onAug. 18, 2016, and provisional application Ser. No. 62/300,547, filed onFeb. 26, 2016. The entire contents of the priority applications arehereby incorporated by reference as if fully set forth.

TECHNICAL FIELD

The present embodiments relate to audio/video (A/V) recording andcommunication devices, including A/V recording and communicationdoorbell systems. In particular, the present embodiments improve thefunctionality of A/V recording and communication devices by facilitatingeasy sharing of video footage recorded by such devices.

BACKGROUND

Home safety is a concern for many homeowners and renters. Those seekingto protect or monitor their homes often wish to have video and audiocommunications with visitors, for example, those visiting an externaldoor or entryway. Audio/Video (A/V) recording and communication devices,such as doorbells, provide this functionality, and can also aid in crimedetection and prevention. For example, audio and/or video captured by anA/V recording and communication device can be uploaded to the cloud andrecorded on a remote server. Subsequent review of the A/V footage canaid law enforcement in capturing perpetrators of home burglaries andother crimes. Further, the presence of one or more A/V recording andcommunication devices on the exterior of a home, such as a doorbell unitat the entrance to the home, acts as a powerful deterrent againstwould-be burglars.

SUMMARY

The various embodiments of the present apparatus, systems, and methodsfor locating a person of interest using shared video footage fromaudio/video (A/V) recording and communication devices have severalfeatures, no single one of which is solely responsible for theirdesirable attributes. Without limiting the scope of the presentembodiments as expressed by the claims that follow, their more prominentfeatures now will be discussed briefly. After considering thisdiscussion, and particularly after reading the section entitled“Detailed Description,” one will understand how the features of thepresent embodiments provide the advantages described herein.

One aspect of the present embodiments includes the realization thatusers of audio/video (A/V) recording and communication devices may fromtime to time desire to share video footage recorded by their devices.For example, when an A/V recording and communication device recordsvideo footage of suspicious activity, or even criminal activity, a userviewing the footage may desire to alert his or her neighbors to thepossible danger posed by the person(s) involved in the suspicious orcriminal activity. It would be advantageous, then, to enhance thefunctionality of A/V recording and communication devices by facilitatingeasy sharing of video footage recorded by such devices with one'sneighbors. In another example, an A/V recording and communication devicemay record video footage of activity that may be of interest to theuser's friends and family (e.g., images of children playing in theyard). It would be advantageous, then, to enhance the functionality ofA/V recording and communication devices by facilitating easy sharing ofvideo footage recorded by such devices with one's friends and family.The present embodiments, as described in detail below, provide these,and other, enhancements. In particular, the present embodiments enablevideo footage captured by A/V recording and communication devices to bereadily uploaded to the cloud and shared with anyone of the user'schoosing, including neighbors, friends, and family. In addition, thepresent embodiments improve upon and solve the problem of video footagecaptured by A/V recording and communication devices being accessibleonly to the owner of the A/V recording and communication device, whichlimits the ability of such devices to help stop crime.

Another aspect of the present embodiments includes the realization thatA/V recording and communication devices, such as A/V recording andcommunication doorbells, are very well adapted for capturing audioand/or video of criminal activity, but not every person owns such adevice. Further, many people who do not own such devices do own othertypes of devices, including client devices such as smartphones, that areequipped with cameras and microphones and are also capable of capturingaudio and/or video of criminal activity. It would be advantageous, then,to provide a network that facilitated the sharing of audio and/or videoof criminal activity regardless of what type of device captured theaudio and/or video. It would be even more advantageous if such a networkenabled communication between users who own A/V recording andcommunication devices, such as A/V recording and communicationdoorbells, and users who do not own such devices. And it would be stillmore advantageous if such a network facilitated the identification ofpersons engaged in criminal activity. The present embodiments providesuch a network.

Another aspect of the present embodiments includes the realization thatmembers of a neighborhood (may also be referred to as “network ofusers”) may benefit from the capability of locating a person ofinterest, initially identified by a first user, on image data capturedby other users. In various embodiments, a neighborhood may include agrouping of members (may also be referred to as “users”) sharinginformation using a neighborhood platform running on each user's clientdevice. For example, the neighborhood platform may include aneighborhood alert feed that allows members to post videos, photos,and/or texts to alert other members of possible suspicious activity inthe neighborhood using a share signal. In some embodiments, a first usermay share first image data that includes a person of interest committinga criminal act or acting suspiciously. In such embodiments, other users,such as a second user, may see the shared first image data in theirneighborhood feed and be asked for permission to search second imagedata captured by devices associated with the second user for a match ofthe person of interest. Further, if the person of interest is found inthe second image data, the matched second image data may be appended tothe first image data of the person of interest and further shared toother users of the network. In other embodiments, a first user may nothave video but may still share a text-based description of a person ofinterest. In such embodiments, other users, such as the second user, maysee the shared text-based description of the person of interest and beasked for permission to search the second image data for a match of thetext-based description of the person of interest. In addition, if theperson of interest is found in the second image data, the matched secondimage data may be included with the text-based description of the personof interest and further shared to other users of the network. In theseways, neighborhood safety may be enhanced by tracking movement andactivity of the person of interest and providing multiple data pointsfor users of the network to see suspicious and/or criminal patterns inthe neighborhood. The present embodiments provide these advantages andenhancements, as described below.

In a first aspect, a method for sharing video footage captured byaudio/video (A/V) recording and communication devices is provided, themethod comprising: receiving, from a first client device associated witha first A/V recording and communication device, at a backend server innetwork communication with the first A/V recording and communicationdevice, a share signal including first image data captured by a cameraof the first A/V recording and communication device, the first imagedata including a person of interest, the share signal including acommand to share the first image data with a network of users;receiving, from a second A/V recording and communication device, at thebackend server in network communication with the second A/V recordingand communication device, second image data captured by a camera of thesecond A/V recording and communication device; transmitting, from thebackend server to a second client device associated with the second A/Vrecording and communication device, the first image data that includesthe person of interest and a request to check the second image data forthe person of interest; receiving, from the second client device at thebackend server, a locate person command signal, in response to therequest to check the second image data for the person of interest;searching the second image data received from the second A/V recordingand communication device for a match of the person of interest in thefirst image data; and when a match of the person of interest is found inthe second image data, generating and transmitting an alert signal tothe second client device, wherein the alert signal includes anotification that the person of interest was matched in the second imagedata.

In an embodiment of the first aspect, the alert signal, transmitted tothe second client device, includes the second image data of the matchedperson of interest.

In another embodiment of the first aspect, the alert signal, transmittedto the second client device, includes a request for permission to sharethe second image data of the matched person of interest with the networkof users.

In another embodiment of the first aspect, the method further comprisesreceiving, from the second client device, an append signal, in responseto the request for permission to share the second image data of thematched person of interest, wherein the append signal includes a commandto append the second image data of the matched person of interest ontothe shared first image data of the person of interest.

In another embodiment of the first aspect, the method further comprisestransmitting, to the network of users, the first image data and thesecond image data of the matched person of interest.

In another embodiment of the first aspect, the searching the secondimage data for the match of the person of interest is performed using atleast one of facial recognition, color matching schemes, and a bodybuild score.

In another embodiment of the first aspect, the method further comprisesconfirming, by a human operator, the match of the person of interest inthe second image data.

In another embodiment of the first aspect, the searching the secondimage data for the match of the person of interest is restricted to asubset of the second image data captured during a predetermined lengthof time.

In another embodiment of the first aspect, the method further comprisesreceiving, from the second client device at the backend server, anautomatic locate command signal, and in response activating a settingfor automatically identifying a further person of interest and searchingthe second image data for a match of the further person of interest inthe second image data each time a new share signal is received includingthe further person of interest.

In a second aspect, a method for sharing video footage captured byaudio/video (A/V) recording and communication devices is provided, themethod comprising: receiving, from a first client device, at a backendserver in network communication with the first client device, atext-based description of a person of interest; receiving, from an A/Vrecording and communication device, at the backend server in networkcommunication with the A/V recording and communication device, imagedata captured by a camera of the A/V recording and communication device;searching the image data for a match of the text-based description ofthe person of interest; transmitting, from the backend server to asecond client device associated with the A/V recording and communicationdevice, the matched image data and a request to confirm that the matchedimage data includes the person of interest; and receiving, from thesecond client device, confirmation that the matched image data includesthe person of interest.

In an embodiment of the second aspect, the method further comprisestransmitting, to the second client device, a request to share thematched image data with a user associated with the first client device.

In another embodiment of the second aspect, the method further comprisesreceiving, from the second client device at the backend server, aconfirmation to share the matched image data with the first clientdevice.

In another embodiment of the second aspect, the method further comprisestransmitting, to the first client device, the matched image data and arequest to confirm that the matched image data includes the person ofinterest.

In another embodiment of the second aspect, the method further comprisesreceiving, from the first client device at the backend server, aconfirmation that the matched image data includes the person ofinterest.

In another embodiment of the second aspect, the method further comprisestransmitting the matched image data to a network of users.

In another embodiment of the second aspect, the method further comprisestransmitting, to the second client device, a request to share thematched image data with a network of users.

In another embodiment of the second aspect, the method further comprisesreceiving, from the second client device at the backend server, aconfirmation to share the matched image data with the network of users.

In another embodiment of the second aspect, the method further comprisestransmitting the matched image data to the network of users.

In another embodiment of the second aspect, the searching the image datafor a match of the text-based description of the person of interest isperformed using natural language processing.

In another embodiment of the second aspect, the searching the image datafor a match of the text-based description of the at least one person ofinterest is performed by comparing a text-based description of the imagedata with the received text-based description of the person of interest.

In a third aspect, a method for sharing recorded video footage fromaudio/video (A/V) recording and communication devices is provided, themethod comprising: receiving, from a backend server, at a second clientdevice associated with a second A/V recording and communication device,first image data captured by a camera of a first A/V recording andcommunication device, the first image data including a person ofinterest; displaying, on a display of the second client device, thefirst image data that includes the person of interest; receiving, fromthe backend server, at the second client device, a second image dataaccess request signal requesting permission to access second image datato search for a match of the person of interest, wherein the secondimage data is captured using a camera of the second A/V recording andcommunication device; displaying, on the display of the second clientdevice, a request to access the second image data to search for a matchof the person of interest; receiving a locate person command input froma user associated with the second client device; in response to thelocate person command input, transmitting, from the second client deviceto the backend server, a locate person command signal; and receiving,from the backend server, at the second client device, an alert signal,wherein the alert signal includes a notification that the person ofinterest was matched in the second image data.

In an embodiment of the third aspect, the alert signal includes thesecond image data of the matched person of interest.

In another embodiment of the third aspect, the alert signal includes asecond image data share request signal requesting permission to sharethe second image data of the matched person of interest to a network ofusers.

In another embodiment of the third aspect, the method further comprises:displaying, on the display of the second client device, a request toshare the second image data with the network of users; receiving anappend input from the user associated with the second client device; andin response to the append input, transmitting, from the second clientdevice to the backend server, an append signal, wherein the appendsignal includes a command to append the second image data of the matchedperson of interest onto the first image data of the person of interestand share the appended second and first image data with the network ofusers.

In another embodiment of the third aspect, the method further comprises:displaying, on the display of the second client device, a request toautomatically grant access to the second image data to search for amatch of a further person of interest; receiving an automatic locateperson command input from the user associated with the second clientdevice; and in response to the automatic locate person command input,transmitting, from the second client device to the backend server, anautomatic locate command signal, wherein the automatic locate commandsignal grants permission to access the second image data to search for amatch of the further person of interest, each time a new share signalincludes new image data that includes the further person of interest.

In a fourth aspect, a non-transitory machine-readable medium storing aclient application for sharing recorded video from audio/video (A/V)recording and communication devices is provided, the client applicationcomprising a set of instructions executable by a processor of a clientdevice, which when executed configures the client device to: receive,from a backend server, a share signal including first image datacaptured by a camera of a first A/V recording and communication device,wherein the first image data includes a person of interest; display, ona display of the client device, the first image that includes the personof interest; receive, from the backend server, a second image dataaccess request signal requesting permission to access second image datato search for a match of the person of interest, wherein the secondimage data is captured using a camera of a second A/V recording andcommunication device associated with the client device; display, on thedisplay of the client device, a request to access the second image datato search for a match of the person of interest found in the first imagedata; receive a locate person command input from a user associated withthe client device; in response to the locate person command input,transmit to the backend server, a locate person command signal; andreceive, from the backend server, an alert signal, wherein the alertsignal includes a notification that the person of interest was matchedin the second image data.

In an embodiment of the fourth aspect, the alert signal includes thesecond image data of the matched person of interest.

In another embodiment of the fourth aspect, the alert signal includes asecond image data share request signal requesting permission to sharethe second image data of the matched person of interest to a network ofusers.

In another embodiment of the fourth aspect, the client application, whenexecuted by the processor of the client device, further configures theclient device to: display, on the display of the client device, arequest to share the second image data with the network of users;receive an append input from the user associated with the client device;and in response to the append input, transmit, to the backend server, anappend signal, wherein the append signal includes a command to appendthe second image data of the matched person of interest onto the firstimage data of the person of interest and share the appended second andfirst image data with the network of users.

In another embodiment of the fourth aspect, the client application, whenexecuted by the processor of the client device, further configures theclient device to: display, on the display of the client device, arequest to automatically grant access to the second image data to searchfor a match of a further person of interest; receive an automatic locateperson command input from the user associated with the client device;and in response to the automatic locate person command input, transmit,to the backend server, an automatic locate command signal, wherein theautomatic locate command signal grants permission to access the secondimage data to search for a match of the further person of interest, eachtime a new share signal includes new image data that includes thefurther person of interest.

BRIEF DESCRIPTION OF THE DRAWINGS

The various embodiments of the present apparatus, systems, and methodsfor locating a person of interest using shared video footage fromaudio/video (A/V) recording and communication devices now will bediscussed in detail with an emphasis on highlighting the advantageousfeatures. These embodiments depict the novel and non-obvious apparatus,systems, and methods for locating a person of interest using sharedvideo footage from A/V recording and communication devices shown in theaccompanying drawings, which are for illustrative purposes only. Thesedrawings include the following figures, in which like numerals indicatelike parts:

FIG. 1 is a functional block diagram illustrating a system for streamingand storing A/V content captured by an audio/video (A/V) recording andcommunication device according to the present embodiments;

FIG. 2 is a front view of an A/V recording and communication doorbellaccording to an aspect of the present disclosure;

FIG. 3 is a rear view of the A/V recording and communication doorbell ofFIG. 2;

FIG. 4 is a left side view of the A/V recording and communicationdoorbell of FIG. 2 attached to a mounting bracket according to an aspectof the present disclosure;

FIG. 5 is cross-sectional right side view of the A/V recording andcommunication doorbell of FIG. 2;

FIG. 6 is an exploded view of the A/V recording and communicationdoorbell and the mounting bracket of FIG. 4;

FIG. 7 is a rear view of the mounting bracket of FIG. 4;

FIGS. 8A and 8B are top and bottom views, respectively, of the A/Vrecording and communication doorbell and the mounting bracket of FIG. 4;

FIGS. 9A and 9B are top and front views, respectively, of a passiveinfrared sensor holder of the A/V recording and communication doorbellof FIG. 2;

FIGS. 10A and 10B are top and front views, respectively, of a passiveinfrared sensor holder assembly of the A/V recording and communicationdoorbell of FIG. 2;

FIG. 11 is a top view of the passive infrared sensor assembly of FIG.10A and a field of view thereof according to an aspect of the presentdisclosure;

FIG. 12 is a functional block diagram of the components of the A/Vrecording and communication doorbell of FIG. 2;

FIG. 13 is a flowchart illustrating a process for a A/V recording andcommunication doorbell according to an aspect of the present disclosure;

FIG. 14 is a flowchart illustrating another process for a A/V recordingand communication doorbell according to an aspect of the presentdisclosure;

FIG. 15 is a flowchart illustrating another process for a A/V recordingand communication doorbell according to an aspect of the presentdisclosure;

FIG. 16 is a functional block diagram illustrating a system for sharingvideo footage from audio/video recording and communication devicesaccording to the present embodiments;

FIG. 17 is a top plan view of a neighborhood with a plurality of A/Vrecording and communication doorbells according to an aspect of thepresent disclosure;

FIG. 18 is a sequence diagram illustrating a process for sharing videofootage from an A/V recording and communication doorbell according to anaspect of the present disclosure;

FIG. 19 is a flowchart illustrating another process for sharing videofootage from an A/V recording and communication doorbell according to anaspect of the present disclosure;

FIGS. 20-24 are screenshots of a graphical user interface (GUI)illustrating aspects of a process for sharing video footage from an A/Vrecording and communication device according to an aspect of the presentdisclosure;

FIGS. 25-29 are screenshots of a graphical user interface (GUI)illustrating aspects of another process for sharing video footage froman A/V recording and communication device according to an aspect of thepresent disclosure;

FIG. 30 is a sequence diagram illustrating another process for sharingvideo footage from an A/V recording and communication doorbell accordingto an aspect of the present disclosure;

FIG. 31 is a flowchart illustrating another process for sharing videofootage from an A/V recording and communication doorbell according to anaspect of the present disclosure;

FIGS. 32-37 are screenshots of a graphical user interface (GUI)illustrating aspects of another process for sharing video footage froman A/V recording and communication device according to an aspect of thepresent disclosure;

FIG. 38 is a sequence diagram illustrating another process for sharingvideo footage from an A/V recording and communication doorbell accordingto an aspect of the present disclosure;

FIG. 39 is a flowchart illustrating another process for sharing videofootage from an A/V recording and communication doorbell according to anaspect of the present disclosure;

FIG. 40 is a flowchart illustrating another process for sharing videofootage from an A/V recording and communication doorbell according to anaspect of the present disclosure;

FIG. 41 is a sequence diagram illustrating another process for sharingvideo footage from an A/V recording and communication doorbell accordingto an aspect of the present disclosure;

FIG. 42 is a flowchart illustrating another process for sharing videofootage from an A/V recording and communication doorbell according to anaspect of the present disclosure;

FIG. 43 is a functional block diagram illustrating a system for sharingvideo footage from A/V recording and communication devices according tothe present embodiments;

FIG. 44 is a functional block diagram of a client device on which thepresent embodiments may be implemented according to various aspects ofthe present disclosure;

FIG. 45 is a functional block diagram of a general-purpose computingsystem on which the present embodiments may be implemented according tovarious aspects of present disclosure;

FIG. 46 is a screenshot of a graphical user interface (GUI) illustratingaspects of another process for sharing video footage from an A/Vrecording and communication device according to an aspect of the presentdisclosure;

FIG. 47 is a functional block diagram illustrating a system forcommunicating in a network according to various aspects of the presentdisclosure;

FIG. 48 is a functional block diagram illustrating one embodiment of afirst A/V recording and communication device according to variousaspects of the present disclosure;

FIG. 49 is a functional block diagram illustrating one embodiment of asecond A/V recording and communication device according to variousaspects of the present disclosure;

FIG. 50 is a functional block diagram illustrating one embodiment of afirst client device according to various aspects of the presentdisclosure;

FIG. 51 is a functional block diagram illustrating one embodiment of asecond client device according to various aspects of the presentdisclosure;

FIG. 52 is a functional block diagram illustrating one embodiment of abackend device according to various aspects of the present disclosure;

FIGS. 53 and 54 are flowcharts illustrating embodiments of processes forsearching second image data for a match of a person of interest providedin first image data according to various aspects of the presentdisclosure;

FIGS. 55 and 56 are flowcharts illustrating embodiments of processes forsearching image data for a match of a person of interest provided in atext-based description according to various aspects of the presentdisclosure;

FIGS. 57 and 58 are sequence diagrams illustrating embodiments ofprocesses for searching second image data for a match of a person ofinterest according to various aspects of the present disclosure; and

FIG. 59 is a functional block diagram illustrating a system forcommunicating in a network using various devices according to variousaspects of the present disclosure.

DETAILED DESCRIPTION

The following detailed description describes the present embodimentswith reference to the drawings. In the drawings, reference numbers labelelements of the present embodiments. These reference numbers arereproduced below in connection with the discussion of the correspondingdrawing features.

The embodiments of the present apparatus, systems, and methods forlocating a person of interest using shared video footage fromaudio/video (A/V) recording and communication devices are describedbelow with reference to the figures. These figures, and their writtendescriptions, indicate that certain components of the apparatus areformed integrally, and certain other components are formed as separatepieces. Those of ordinary skill in the art will appreciate thatcomponents shown and described herein as being formed integrally may inalternative embodiments be formed as separate pieces. Those of ordinaryskill in the art will further appreciate that components shown anddescribed herein as being formed as separate pieces may in alternativeembodiments be formed integrally. Further, as used herein the termintegral describes a single unitary piece.

With reference to FIG. 1, the present embodiments include an audio/video(A/V) recording and communication device, such as a doorbell 100. Whilethe present disclosure provides numerous examples of methods and systemsincluding A/V recording and communication doorbells, the presentembodiments are equally applicable for A/V recording and communicationdevices other than doorbells. For example, the present embodiments mayinclude one or more A/V recording and communication security camerasinstead of, or in addition to, one or more A/V recording andcommunication doorbells. An example A/V recording and communicationsecurity camera may include substantially all of the structure andfunctionality of the doorbells described herein, but without the frontbutton and related components.

The A/V recording and communication doorbell 100 may be located near theentrance to a structure (not shown), such as a dwelling, a business, astorage facility, etc. The A/V recording and communication doorbell 100includes a camera 102, a microphone 104, and a speaker 106. The camera102 may comprise, for example, a high definition (HD) video camera, suchas one capable of capturing video images at an image display resolutionof 720p or better. While not shown, the A/V recording and communicationdoorbell 100 may also include other hardware and/or components, such asa housing, one or more motion sensors (and/or other types of sensors), abutton, etc. The A/V recording and communication doorbell 100 mayfurther include similar componentry and/or functionality as the wirelesscommunication doorbells described in US Patent Application PublicationNos. 2015/0022620 (application Ser. No. 14/499,828) and 2015/0022618(application Ser. No. 14/334,922), both of which are incorporated hereinby reference in their entireties as if fully set forth.

With further reference to FIG. 1, the A/V recording and communicationdoorbell 100 communicates with a user's network 110, which may be forexample a wired and/or wireless network. If the user's network 110 iswireless, or includes a wireless component, the network 110 may be aWi-Fi network compatible with the IEEE 802.11 standard and/or otherwireless communication standard(s). The user's network 110 is connectedto another network 112, which may comprise, for example, the Internetand/or a public switched telephone network (PSTN). As described below,the A/V recording and communication doorbell 100 may communicate withthe user's client device 114 via the user's network 110 and the network112 (Internet/PSTN). The user's client device 114 may comprise, forexample, a mobile telephone (may also be referred to as a cellulartelephone), such as a smartphone, a personal digital assistant (PDA), oranother communication and/or computing device. The user's client device114 comprises a display (not shown) and related components capable ofdisplaying streaming and/or recorded video images. The user's clientdevice 114 may also comprise a speaker and related components capable ofbroadcasting streaming and/or recorded audio, and may also comprise amicrophone. The A/V recording and communication doorbell 100 may alsocommunicate with one or more remote storage device(s) 116 (may bereferred to interchangeably as “cloud storage device(s)”), one or moreservers 118, and/or a backend API (application programming interface)120 via the user's network 110 and the network 112 (Internet/PSTN).While FIG. 1 illustrates the storage device 116, the server 118, and thebackend API 120 as components separate from the network 112, it is to beunderstood that the storage device 116, the server 118, and/or thebackend API 120 may be considered to be components of the network 112.

The network 112 may be any wireless network or any wired network, or acombination thereof, configured to operatively couple theabove-mentioned modules, devices, and systems as shown in FIG. 1. Forexample, the network 112 may include one or more of the following: aPSTN (public switched telephone network), the Internet, a localintranet, a PAN (Personal Area Network), a LAN (Local Area Network), aWAN (Wide Area Network), a MAN (Metropolitan Area Network), a virtualprivate network (VPN), a storage area network (SAN), a frame relayconnection, an Advanced Intelligent Network (AIN) connection, asynchronous optical network (SONET) connection, a digital T1, T3, E1 orE3 line, a Digital Data Service (DDS) connection, a DSL (DigitalSubscriber Line) connection, an Ethernet connection, an ISDN (IntegratedServices Digital Network) line, a dial-up port such as a V.90, V.34, orV.34bis analog modem connection, a cable modem, an ATM (AsynchronousTransfer Mode) connection, or an FDDI (Fiber Distributed Data Interface)or CDDI (Copper Distributed Data Interface) connection. Furthermore,communications may also include links to any of a variety of wirelessnetworks, including WAP (Wireless Application Protocol), GPRS (GeneralPacket Radio Service), GSM (Global System for Mobile Communication),CDMA (Code Division Multiple Access), TDMA (Time Division MultipleAccess), FDMA (Frequency Division Multiple Access), and/or OFDMA(Orthogonal Frequency Division Multiple Access) cellular phone networks,GPS, CDPD (cellular digital packet data), RIM (Research in Motion,Limited) duplex paging network, Bluetooth radio, or an IEEE 802.11-basedradio frequency network. The network can further include or interfacewith any one or more of the following: RS-232 serial connection,IEEE-1394 (Firewire) connection, Fibre Channel connection, IrDA(infrared) port, SCSI (Small Computer Systems Interface) connection, USB(Universal Serial Bus) connection, or other wired or wireless, digitalor analog, interface or connection, mesh or Digi® networking.

According to one or more aspects of the present embodiments, when aperson (may be referred to interchangeably as “visitor”) arrives at theA/V recording and communication doorbell 100, the A/V recording andcommunication doorbell 100 detects the visitor's presence and beginscapturing video images within a field of view of the camera 102. The A/Vrecording and communication doorbell 100 may also capture audio throughthe microphone 104. The A/V recording and communication doorbell 100 maydetect the visitor's presence using a motion sensor, and/or by detectingthat the visitor has depressed the button on the A/V recording andcommunication doorbell 100.

In response to the detection of the visitor, the A/V recording andcommunication doorbell 100 sends an alert to the user's client device114 (FIG. 1) via the user's network 110 and the network 112. The A/Vrecording and communication doorbell 100 also sends streaming video, andmay also send streaming audio, to the user's client device 114. If theuser answers the alert, two-way audio communication may then occurbetween the visitor and the user through the A/V recording andcommunication doorbell 100 and the user's client device 114. The usermay view the visitor throughout the duration of the call, but thevisitor cannot see the user (unless the A/V recording and communicationdoorbell 100 includes a display, which it may in some embodiments).

The video images captured by the camera 102 of the A/V recording andcommunication doorbell 100 (and the audio captured by the microphone104) may be uploaded to the cloud and recorded on the remote storagedevice 116 (FIG. 1). In some embodiments, the video and/or audio may berecorded on the remote storage device 116 even if the user chooses toignore the alert sent to his or her client device 114.

With further reference to FIG. 1, the system may further comprise abackend API 120 including one or more components. As discussed infurther detail below, a backend API (application programming interface)may comprise, for example, a server (e.g. a real server, or a virtualmachine, or a machine running in a cloud infrastructure as a service),or multiple servers networked together, exposing at least one API toclient(s) accessing it.

FIGS. 2-4 illustrate an audio/video (A/V) communication doorbell 130according to an aspect of present embodiments. FIG. 2 is a front view,FIG. 3 is a rear view, and FIG. 4 is a left side view of the doorbell130 coupled with a mounting bracket 137. The doorbell 130 includes afaceplate 135 mounted to a back plate 139 (FIG. 3). With reference toFIG. 4, the faceplate 135 has a substantially flat profile. Thefaceplate 135 may comprise any suitable material, including, withoutlimitation, metals, such as brushed aluminum or stainless steel, metalalloys, or plastics. The faceplate 135 protects the internal contents ofthe doorbell 130 and serves as an exterior front surface of the doorbell130.

With reference to FIG. 2, the faceplate 135 includes a button 133 and alight pipe 136. The button 133 and the light pipe 136 may have variousprofiles that may or may not match the profile of the faceplate 135. Thelight pipe 136 may comprise any suitable material, including, withoutlimitation, transparent plastic, that is capable of allowing lightproduced within the doorbell 130 to pass through. The light may beproduced by one or more light-emitting components, such aslight-emitting diodes (LED's), contained within the doorbell 130, asfurther described below. The button 133 may make contact with a buttonactuator (not shown) located within the doorbell 130 when the button 133is pressed by a visitor. When pressed, the button 133 may trigger one ormore functions of the doorbell 130, as further described below.

With reference to FIGS. 2 and 4, the doorbell 130 further includes anenclosure 131 that engages the faceplate 135. In the illustratedembodiment, the enclosure 131 abuts an upper edge 135T (FIG. 2) of thefaceplate 135, but in alternative embodiments one or more gaps betweenthe enclosure 131 and the faceplate 135 may facilitate the passage ofsound and/or light through the doorbell 130. The enclosure 131 maycomprise any suitable material, but in some embodiments the material ofthe enclosure 131 preferably permits infrared light to pass through frominside the doorbell 130 to the environment and vice versa. The doorbell130 further includes a lens 132. In some embodiments, the lens maycomprise a Fresnel lens, which may be patterned to deflect incominglight into one or more infrared sensors located within the doorbell 130.The doorbell 130 further includes a camera 134, which captures videodata when activated, as described below.

FIG. 3 is a rear view of the doorbell 130, according to an aspect of thepresent embodiments. As illustrated, the enclosure 131 may extend fromthe front of the doorbell 130 around to the back thereof and may fitsnugly around a lip of the back plate 139. The back plate 139 maycomprise any suitable material, including, without limitation, metals,such as brushed aluminum or stainless steel, metal alloys, or plastics.The back plate 139 protects the internal contents of the doorbell 130and serves as an exterior rear surface of the doorbell 130. Thefaceplate 135 may extend from the front of the doorbell 130 and at leastpartially wrap around the back plate 139, thereby allowing a coupledconnection between the faceplate 135 and the back plate 139. The backplate 139 may have indentations in its structure to facilitate thecoupling.

With further reference to FIG. 3, spring contacts 140 may provide powerto the doorbell 130 when mated with other conductive contacts connectedto a power source. The spring contacts 140 may comprise any suitableconductive material, including, without limitation, copper, and may becapable of deflecting when contacted by an inward force, for example theinsertion of a mating element. The doorbell 130 further comprises aconnector 160, such as a micro-USB or other connector, whereby powerand/or data may be supplied to and from the components within thedoorbell 130. A reset button 159 may be located on the back plate 139,and may make contact with a button actuator (not shown) located withinthe doorbell 130 when the reset button 159 is pressed. When the resetbutton 159 is pressed, it may trigger one or more functions, asdescribed below.

FIG. 4 is a left side profile view of the doorbell 130 coupled to themounting bracket 137, according to an aspect of the present embodiments.The mounting bracket 137 facilitates mounting the doorbell 130 to asurface, such as the exterior of a building, such as a home or office.As illustrated in FIG. 4, the faceplate 135 may extend from the bottomof the doorbell 130 up to just below the camera 134, and connect to theback plate 139 as described above. The lens 132 may extend and curlpartially around the side of the doorbell 130. The enclosure 131 mayextend and curl around the side and top of the doorbell 130, and may becoupled to the back plate 139 as described above. The camera 134 mayprotrude slightly through the enclosure 131, thereby giving it a widerfield of view. The mounting bracket 137 may couple with the back plate139 such that they contact each other at various points in a commonplane of contact, thereby creating an assembly including the doorbell130 and the mounting bracket 137. The couplings described in thisparagraph, and elsewhere, may be secured by, for example and withoutlimitation, screws, interference fittings, adhesives, or otherfasteners. Interference fittings may refer to a type of connection wherea material relies on pressure and/or gravity coupled with the material'sphysical strength to support a connection to a different element.

FIG. 5 is a right side cross-sectional view of the doorbell 130 withoutthe mounting bracket 137. In the illustrated embodiment, the lens 132 issubstantially coplanar with the front surface 131F of the enclosure 131.In alternative embodiments, the lens 132 may be recessed within theenclosure 131 or may protrude outward from the enclosure 131. The camera134 is coupled to a camera printed circuit board (PCB) 147, and a lens134 a of the camera 134 protrudes through an opening in the enclosure131. The camera lens 134 a may be a lens capable of focusing light intothe camera 134 so that clear images may be taken.

The camera PCB 147 may be secured within the doorbell with any suitablefasteners, such as screws, or interference connections, adhesives, etc.The camera PCB 147 comprises various components that enable thefunctionality of the camera 134 of the doorbell 130, as described below.Infrared light-emitting components, such as infrared LED's 168, arecoupled to the camera PCB 147 and may be triggered to activate when alight sensor detects a low level of ambient light. When activated, theinfrared LED's 168 may emit infrared light through the enclosure 131and/or the camera 134 out into the ambient environment. The camera 134,which may be configured to detect infrared light, may then capture thelight emitted by the infrared LED's 168 as it reflects off objectswithin the camera's 134 field of view, so that the doorbell 130 canclearly capture images at night (may be referred to as “night vision”).

With continued reference to FIG. 5, the doorbell 130 further comprises afront PCB 146, which in the illustrated embodiment resides in a lowerportion of the doorbell 130 adjacent a battery 166. The front PCB 146may be secured within the doorbell 130 with any suitable fasteners, suchas screws, or interference connections, adhesives, etc. The front PCB146 comprises various components that enable the functionality of theaudio and light components, as further described below. The battery 166may provide power to the doorbell 130 components while receiving powerfrom the spring contacts 140, thereby engaging in a trickle-chargemethod of power consumption and supply. Alternatively, the doorbell 130may draw power directly from the spring contacts 140 while relying onthe battery 166 only when the spring contacts 140 are not providing thepower necessary for all functions.

With continued reference to FIG. 5, the doorbell 130 further comprises apower PCB 148, which in the illustrated embodiment resides behind thecamera PCB 147. The power PCB 148 may be secured within the doorbell 130with any suitable fasteners, such as screws, or interferenceconnections, adhesives, etc. The power PCB 148 comprises variouscomponents that enable the functionality of the power and device-controlcomponents, as further described below.

With continued reference to FIG. 5, the doorbell 130 further comprises acommunication module 164 coupled to the power PCB 148. The communicationmodule 164 facilitates communication with client devices in one or moreremote locations, as further described below. The connector 160 mayprotrude outward from the power PCB 148 and extend through a hole in theback plate 139. The doorbell 130 further comprises passive infrared(PIR) sensors 144, which are secured on or within a PIR sensor holder143, and the assembly resides behind the lens 132. The PIR sensor holder143 may be secured to the doorbell 130 with any suitable fasteners, suchas screws, or interference connections, adhesives, etc. The PIR sensors144 may be any type of sensor capable of detecting and communicating thepresence of a heat source within their field of view. Further,alternative embodiments may comprise one or more motion sensors eitherin place of or in addition to the PIR sensors 144. The motion sensorsmay be configured to detect motion using any methodology, such as amethodology that does not rely on detecting the presence of a heatsource within a field of view.

FIG. 6 is an exploded view of the doorbell 130 and the mounting bracket137 according to an aspect of the present embodiments. The mountingbracket 137 is configured to be mounted to a mounting surface (notshown) of a structure, such as a home or an office. FIG. 6 shows thefront side 137F of the mounting bracket 137. The mounting bracket 137 isconfigured to be mounted to the mounting surface such that the back side137B thereof faces the mounting surface. In certain embodiments, themounting bracket 137 may be mounted to surfaces of various composition,including, without limitation, wood, concrete, stucco, brick, vinylsiding, aluminum siding, etc., with any suitable fasteners, such asscrews, or interference connections, adhesives, etc. The doorbell 130may be coupled to the mounting bracket 137 with any suitable fasteners,such as screws, or interference connections, adhesives, etc.

With continued reference to FIG. 6, the illustrated embodiment of themounting bracket 137 includes the terminal screws 138. The terminalscrews 138 are configured to receive electrical wires adjacent themounting surface of the structure upon which the mounting bracket 137 ismounted, so that the doorbell 130 may receive electrical power from thestructure's electrical system. The terminal screws 138 are electricallyconnected to electrical contacts 177 of the mounting bracket. If poweris supplied to the terminal screws 138, then the electrical contacts 177also receive power through the terminal screws 138. The electricalcontacts 177 may comprise any suitable conductive material, including,without limitation, copper, and may protrude slightly from the face ofthe mounting bracket 137 so that they may mate with the spring contacts140 located on the back plate 139.

With reference to FIGS. 6 and 7 (which is a rear view of the mountingbracket 137), the mounting bracket 137 further comprises a bracket PCB149. With reference to FIG. 7, the bracket PCB 149 is situated outsidethe doorbell 130, and is therefore configured for various sensors thatmeasure ambient conditions, such as an accelerometer 150, a barometer151, a humidity sensor 152, and a temperature sensor 153. The functionsof these components are discussed in more detail below. The bracket PCB149 may be secured to the mounting bracket 137 with any suitablefasteners, such as screws, or interference connections, adhesives, etc.

FIGS. 8A and 8B are top and bottom views, respectively, of the doorbell130. As described above, the enclosure 131 may extend from the frontface 131F of the doorbell 130 to the back, where it contacts and snuglysurrounds the back plate 139. The camera 134 may protrude slightlybeyond the front face 131F of the enclosure 131, thereby giving thecamera 134 a wider field of view. The mounting bracket 137 may include asubstantially flat rear surface 137R, such that the doorbell 130 and themounting bracket 137 assembly may sit flush against the surface to whichthey are mounted. With reference to FIG. 8B, the lower end of theenclosure 131 may include security screw apertures 141 configured toreceive screws or other fasteners.

FIG. 9A is a top view of the PIR sensor holder 143. The PIR sensorholder 143 may comprise any suitable material, including, withoutlimitation, metals, metal alloys, or plastics. The PIR sensor holder 143is configured to mount the PIR sensors 144 behind the lens 132 such thatthe PIR sensors 144 face out through the lens 132 at varying angles,thereby creating a wide field of view for the PIR sensors 144, anddividing the field of view into zones, as further described below. Withfurther reference to FIG. 9A, the PIR sensor holder 143 includes one ormore faces 178 within or on which the PIR sensors 144 may be mounted. Inthe illustrated embodiment, the PIR sensor holder 143 includes threefaces 178, with each of two outer faces 178 angled at 55° with respectto a center one of the faces 178. In alternative embodiments, the angleformed by adjacent ones of the faces 178 may be increased or decreasedas desired to alter the field of view of the PIR sensors 144.

FIG. 9B is a front view of the PIR sensor holder 143. In the illustratedembodiment, each of the faces 178 includes a through hole 180 in whichthe PIR sensors 144 may be mounted. First and second brackets 182,spaced from one another, extend transversely across the PIR sensorholder 143. Each of the brackets 182 includes notches 184 at either end.The brackets 182 may be used to secure the PIR sensor holder 143 withinthe doorbell 130. In alternative embodiments, the through holes 180 inthe faces 178 may be omitted. For example, the PIR sensors 144 may bemounted directly to the faces 178 without the through holes 180.Generally, the faces 178 may be comprise any structure configured tolocate and secure the PIR sensors 144 in place.

FIGS. 10A and 10B are top and front views, respectively, of a PIR sensorassembly 179, including the PIR sensor holder 143, the lens 132, and aflexible power circuit 145. The PIR sensor holder 143 may be secured toa rear face 132R of the lens 132, as shown, with the brackets 182abutting the rear face 132R of the lens 132. The flexible power circuit145, which may be any material or component capable of delivering powerand/or data to and from the PIR sensors 144, is secured to a rear face143R of the PIR sensor holder 143, and may be contoured to match theangular shape of the PIR sensor holder 143. The flexible power circuit145 may connect to, draw power from, and/or transmit data to and/orfrom, the power PCB 148 (FIG. 5).

FIG. 11 is a top view of the PIR sensor assembly 179 illustrating thefields of view of the PIR sensors 144. Each PIR sensor 144 includes afield of view, referred to as a “zone,” that traces an angle extendingoutward from the respective PIR sensor 144. Zone 1 is the area that isvisible only to Passive Infrared Sensor 144-1. Zone 2 is the area thatis visible only to the PIR sensors 144-1 and 144-2. Zone 3 is the areathat is visible only to Passive Infrared Sensor 144-2. Zone 4 is thearea that is visible only to the PIR sensors 144-2 and 144-3. Zone 5 isthe area that is visible only to Passive Infrared Sensor 144-3. Thedoorbell 130 may be capable of determining the direction that an objectis moving based upon which zones are triggered in a time sequence. Inthe illustrated embodiment, each zone extends across an angle of 110°.In alternative embodiments, each zone may extend across a differentangle, such as one greater than or less than 110°.

FIG. 12 is a functional block diagram of the components within or incommunication with the doorbell 130, according to an aspect of thepresent embodiments. As described above, the bracket PCB 149 maycomprise an accelerometer 150, a barometer 151, a humidity sensor 152,and a temperature sensor 153. The accelerometer 150 may be one or moresensors capable of sensing motion and/or acceleration. The barometer 151may be one or more sensors capable of determining the atmosphericpressure of the surrounding environment in which the bracket PCB 149 maybe located. The humidity sensor 152 may be one or more sensors capableof determining the amount of moisture present in the atmosphericenvironment in which the bracket PCB 149 may be located. The temperaturesensor 153 may be one or more sensors capable of determining thetemperature of the ambient environment in which the bracket PCB 149 maybe located. As described above, the bracket PCB 149 may be locatedoutside the housing of the doorbell 130 so as to reduce interferencefrom heat, pressure, moisture, and/or other stimuli generated by theinternal components of the doorbell 130.

With further reference to FIG. 12, the bracket PCB 149 may furthercomprise terminal screw inserts 154, which may be configured to receivethe terminal screws 138 and transmit power to the electrical contacts177 on the mounting bracket 137 (FIG. 6). The bracket PCB 149 may beelectrically and/or mechanically coupled to the power PCB 148 throughthe terminal screws 138, the terminal screw inserts 154, the springcontacts 140, and the electrical contacts 177. The terminal screws 138may receive electrical wires located at the surface to which thedoorbell 130 is mounted, such as the wall of a building, so that thedoorbell can receive electrical power from the building's electricalsystem. Upon the terminal screws 138 being secured within the terminalscrew inserts 154, power may be transferred to the bracket PCB 149, andto all of the components associated therewith, including the electricalcontacts 177. The electrical contacts 177 may transfer electrical powerto the power PCB 148 by mating with the spring contacts 140.

With further reference to FIG. 12, the front PCB 146 may comprise alight sensor 155, one or more light-emitting components, such as LED's156, one or more speakers 157, and a microphone 158. The light sensor155 may be one or more sensors capable of detecting the level of ambientlight of the surrounding environment in which the doorbell 130 may belocated. LED's 156 may be one or more light-emitting diodes capable ofproducing visible light when supplied with power. The speakers 157 maybe any electromechanical device capable of producing sound in responseto an electrical signal input. The microphone 158 may be anacoustic-to-electric transducer or sensor capable of converting soundwaves into an electrical signal. When activated, the LED's 156 mayilluminate the light pipe 136 (FIG. 2). The front PCB 146 and allcomponents thereof may be electrically coupled to the power PCB 148,thereby allowing data and/or power to be transferred to and from thepower PCB 148 and the front PCB 146.

The speakers 157 and the microphone 158 may be coupled to the cameraprocessor 170 through an audio CODEC 161. For example, the transfer ofdigital audio from the user's client device 114 and the speakers 157 andthe microphone 158 may be compressed and decompressed using the audioCODEC 161, coupled to the camera processor 170. Once compressed by audioCODEC 161, digital audio data may be sent through the communicationmodule 164 to the network 112, routed by one or more servers 118, anddelivered to the user's client device 114. When the user speaks, afterbeing transferred through the network 112, digital audio data isdecompressed by audio CODEC 161 and emitted to the visitor via thespeakers 157.

With further reference to FIG. 12, the power PCB 148 may comprise apower management module 162, a microcontroller 163, the communicationmodule 164, and power PCB non-volatile memory 165. In certainembodiments, the power management module 162 may comprise an integratedcircuit capable of arbitrating between multiple voltage rails, therebyselecting the source of power for the doorbell 130. The battery 166, thespring contacts 140, and/or the connector 160 may each provide power tothe power management module 162. The power management module 162 mayhave separate power rails dedicated to the battery 166, the springcontacts 140, and the connector 160. In one aspect of the presentdisclosure, the power management module 162 may continuously draw powerfrom the battery 166 to power the doorbell 130, while at the same timerouting power from the spring contacts 140 and/or the connector 160 tothe battery 166, thereby allowing the battery 166 to maintain asubstantially constant level of charge. Alternatively, the powermanagement module 162 may continuously draw power from the springcontacts 140 and/or the connector 160 to power the doorbell 130, whileonly drawing from the battery 166 when the power from the springcontacts 140 and/or the connector 160 is low or insufficient. The powermanagement module 162 may also serve as a conduit for data between theconnector 160 and the microcontroller 163.

With further reference to FIG. 12, in certain embodiments themicrocontroller 163 may comprise an integrated circuit including aprocessor core, memory, and programmable input/output peripherals. Themicrocontroller 163 may receive input signals, such as data and/orpower, from the PIR sensors 144, the bracket PCB 149, the powermanagement module 162, the light sensor 155, the microphone 158, and/orthe communication module 164, and may perform various functions asfurther described below. When the microcontroller 163 is triggered bythe PIR sensors 144, the microcontroller 163 may be triggered to performone or more functions, such as those described below with reference toFIG. 14. When the light sensor 155 detects a low level of ambient light,the light sensor 155 may trigger the microcontroller 163 to enable“night vision,” as further described below. The microcontroller 163 mayalso act as a conduit for data communicated between various componentsand the communication module 164.

With further reference to FIG. 12, the communication module 164 maycomprise an integrated circuit including a processor core, memory, andprogrammable input/output peripherals. The communication module 164 mayalso be configured to transmit data wirelessly to a remote networkdevice, and may include one or more transceivers (not shown). Thewireless communication may comprise one or more wireless networks, suchas, without limitation, Wi-Fi, cellular, Bluetooth, and/or satellitenetworks. The communication module 164 may receive inputs, such as powerand/or data, from the camera PCB 147, the microcontroller 163, thebutton 133, the reset button 159, and/or the power PCB non-volatilememory 165. When the button 133 is pressed, the communication module 164may be triggered to perform one or more functions, such as thosedescribed below with reference to FIG. 13. When the reset button 159 ispressed, the communication module 164 may be triggered to erase any datastored at the power PCB non-volatile memory 165 and/or at the camera PCBmemory 169. The communication module 164 may also act as a conduit fordata communicated between various components and the microcontroller163. The power PCB non-volatile memory 165 may comprise flash memoryconfigured to store and/or transmit data. For example, in certainembodiments the power PCB non-volatile memory 165 may comprise serialperipheral interface (SPI) flash memory.

With further reference to FIG. 12, the camera PCB 147 may comprisecomponents that facilitate the operation of the camera 134. For example,an imager 171 may comprise a video recording sensor and/or a camerachip. In one aspect of the present disclosure, the imager 171 maycomprise a complementary metal-oxide semiconductor (CMOS) array, and maybe capable of recording high definition (720p or better) video files. Acamera processor 170 may comprise an encoding and compression chip. Insome embodiments, the camera processor 170 may comprise a bridgeprocessor. The camera processor 170 may process video recorded by theimager 171 and audio recorded by the microphone 158, and may transformthis data into a form suitable for wireless transfer by thecommunication module 164 to a network. The camera PCB memory 169 maycomprise volatile memory that may be used when data is being buffered orencoded by the camera processor 170. For example, in certain embodimentsthe camera PCB memory 169 may comprise synchronous dynamic random accessmemory (SD RAM). IR LED's 168 may comprise light-emitting diodes capableof radiating infrared light. IR cut filter 167 may comprise a systemthat, when triggered, configures the imager 171 to see primarilyinfrared light as opposed to visible light. When the light sensor 155detects a low level of ambient light (which may comprise a level thatimpedes the performance of the imager 171 in the visible spectrum), theIR LED's 168 may shine infrared light through the doorbell 130 enclosureout to the environment, and the IR cut filter 167 may enable the imager171 to see this infrared light as it is reflected or refracted off ofobjects within the field of view of the doorbell. This process mayprovide the doorbell 130 with the “night vision” function mentionedabove.

FIG. 13 is a flowchart illustrating one embodiment of a processaccording to an aspect of the present disclosure. At block B200, avisitor presses the button 133 on the doorbell 130. At block B202, thecommunication module 164 sends a request to a network device. Once thenetwork device receives the request, at block B204 the network devicemay connect the doorbell 130 to the user's client device 114 through theuser's network 110 and the network 112. In block B206, the doorbell 130may record available audio and/or video data using the camera 134, themicrophone 158, and/or any other sensor available. At block B208, theaudio and/or video data is transmitted to the user's client device 114.At block B210, the user may receive a notification on his or her clientdevice 114 prompting him or her to either accept or deny. If the userdenies the notification, then the process advances to block B214, wherethe audio and/or video data is recorded and stored at a cloud server.The session then ends at block B216 and the connection between thedoorbell 130 and the user's client device 114 is terminated. If,however, the user elects to accept the notification, then at block B212the user communicates with the visitor through the user's client device114 while being provided audio and/or video data captured by the camera134, the microphone 158, and/or other sensors. At the end of the call,the user may terminate the connection between the user's client device114 and the doorbell 130 and the session ends at block B216. In someembodiments, the audio and/or video data may be recorded and stored at acloud server even if the user accepts the notification and communicateswith the visitor through the user's client device 114.

FIG. 14 is a flowchart illustrating another embodiment of a processaccording to an aspect of the present disclosure. At block B300, anobject may move into the field of view of one or more of the PIR sensors144. At block B302, the PIR sensors 144 may trigger the microcontroller163, which may then trigger the communication module 164 to send arequest to a network device. At block B304, the network device mayconnect the doorbell 130 to the user's client device 114 through theuser's network 110 and the network 112. At block B306, the doorbell 130may record available audio and/or video data using the camera 134, themicrophone 158, and/or any other available sensor, and stream the datato the user's client device 114. At block B308, the user may receive anotification prompting the user to either accept or deny thenotification. If the notification is accepted, then at block B310 a thelive audio/video data may be displayed on the user's client device 114,thereby allowing the user surveillance from the perspective of thedoorbell 130. When the user is satisfied with this function, the usermay sever the connection at block B312, whereby the session ends. If,however, at block B308 the user denies the notification, or ignores thenotification and a specified time interval elapses, then the connectionbetween the doorbell 130 and the user's client device 114 is terminatedand the audio/video data is recorded and stored at a cloud server atblock B310 b, such that the user may view the audio/video data later attheir convenience. The doorbell 130 may be configured to record for aspecified period of time in the event the notification in block B308 isdenied or ignored. If such a time period is set, the doorbell 130 mayrecord data for that period of time before ceasing operation at blockB312 thereby ending the session.

FIG. 15 is a flowchart illustrating another embodiment of a processaccording to an aspect of the present disclosure. At block B400, theuser may select a “snooze time-out,” which is a time period during whichthe doorbell 130 may deactivate or otherwise not respond to stimuli(such as light, sound, or heat signatures) after an operation isperformed, e.g. a notification is either accepted or denied/ignored. Forexample, the user may set a snooze time-out of 15 minutes. At blockB402, an object moves into the field of view of one or more of the PIRsensors 144. At block B404, the microcontroller 163 may trigger thecommunication module 164 to send a request to a network device. In blockB406, the network device may connect the doorbell 130 to the user'sclient device 114 through the user's network 110 and the network 112. Atblock B408, audio/video data captured by the doorbell 130 may bestreamed to the user's client device 114. At block B410, the user mayreceive a notification prompting the user to either accept ordeny/ignore the request. If the request is denied or ignored, then atblock B412 b audio/video data may be recorded and stored at a cloudserver. After the doorbell 130 finishes recording, the objects mayremain in the PIR sensor 144 field of view at block B414. In block B416,the microcontroller 163 waits for the “snooze time” to elapse, e.g. 15minutes, before triggering the communication module 164 to submitanother request to the network device. After the snooze time, e.g. 15minutes, elapses, the process moves back to block B404 and progresses asdescribed above. The cycle may continue like this until the user acceptsthe notification request at block B410. The process then moves to blockB412 a, where live audio and/or video data is displayed on the user'sclient device 114, thereby allowing the user surveillance from theperspective of the doorbell 130. At the user's request, the connectionmay be severed and the session ends at block B418. At this point theuser may elect for the process to revert back to block B416, wherebythere may be no further response until the snooze time, e.g. 15 minutes,has elapsed from the end of the previous session, or the user may electfor the process to return to block B402 and receive a notification thenext time an object is perceived by one or more of the PIR sensors 144.

As discussed above, the present disclosure provides numerous examples ofmethods and systems including A/V recording and communication doorbells,but the present embodiments are equally applicable for A/V recording andcommunication devices other than doorbells. For example, the presentembodiments may include one or more A/V recording and communicationsecurity cameras instead of, or in addition to, one or more A/Vrecording and communication doorbells. An example A/V recording andcommunication security camera may include substantially all of thestructure and functionality of the doorbell 130, but without the frontbutton 133, the button actuator, and/or the light pipe 136. An exampleA/V recording and communication security camera may further omit othercomponents, such as, for example, the bracket PCB 149 and itscomponents.

As described above, one aspect of the present embodiments includes therealization that users of audio/video (A/V) recording and communicationdevices may from time to time desire to share video footage recorded bytheir devices. For example, when an A/V recording and communicationdevice records video footage of suspicious activity, or even criminalactivity, a user viewing the footage may desire to alert his or herneighbors to the possible danger posed by the person(s) involved in thesuspicious or criminal activity. It would be advantageous, then, toenhance the functionality of A/V recording and communication devices byfacilitating easy sharing of video footage recorded by such devices withone's neighbors. In another example, an A/V recording and communicationdevice may record video footage of activity that may be of interest tothe user's friends and family (e.g., images of children playing in theyard). It would be advantageous, then, to enhance the functionality ofA/V recording and communication devices by facilitating easy sharing ofvideo footage recorded by such devices with one's friends and family.The present embodiments, as described in detail below, provide these,and other, enhancements. In particular, the present embodiments enablevideo footage captured by A/V recording and communication devices to bereadily uploaded to the cloud and shared with anyone of the user'schoosing, including neighbors, friends, and family.

FIG. 16 illustrates a system 500 for sharing video footage from A/Vrecording and communication devices according to the presentembodiments. The illustrated system 500 includes a first A/V recordingand communication doorbell 502 (labeled “A/V Doorbell #1”). The firstA/V doorbell 502 may have, for example, similar components and/orfunctionality as the doorbell 130 described herein. Alternatively, thefirst A/V doorbell 502 may have different components and/orfunctionality as the doorbell 130, but may nevertheless be capable ofrecording video footage and/or audio and wirelessly transmitting therecorded video footage and/or audio. In certain embodiments, the firstA/V doorbell 502 may not be a doorbell at all, but may be, for example,an A/V recording and communication security camera.

With further reference to FIG. 16, the system 500 further includes afirst client device 504 (labeled “Client Device #1”) associated with thefirst A/V doorbell 502. The first client device 504 and the first A/Vdoorbell 502 may be owned by and/or controlled by the same user. Thefirst client device 504 may have, for example, similar components and/orfunctionality as the user's client device 114 described herein, and maycomprise, for example, a mobile telephone (may also be referred to as acellular telephone), such as a smartphone, a personal digital assistant(PDA), or another communication and/or computing device. The system 500further includes a network 506. The network 506, which may comprise, forexample, the Internet and/or a public switched telephone network (PSTN),includes a plurality of network devices, such as one or more servers,routers, switches, storage devices, etc. (not shown). The system 500further includes a plurality of other A/V doorbells 508, 510 (labeled“A/V Doorbell #2” through “A/V Doorbell # N”) and a plurality of otherclient devices 512, 514 (labeled “Client Device #2” through “ClientDevice # N”). The other client devices 512, 514 are each associated witha corresponding one of the other A/V doorbells 508, 510. The other A/Vdoorbells 508, 510 may have, for example, similar components and/orfunctionality as the first A/V doorbell 502, and the other clientdevices 512, 514 may have, for example, similar components and/orfunctionality as the first client device 504.

In the system 500 of FIG. 16, any of the A/V doorbells may record videofootage from an area within a field of view of the respective doorbell.The owner (or a user) of the doorbell that has recorded video footagemay share the video footage with one or more other owners/users of theother A/V doorbells. The determination of which users will receive anotification of the shared video footage may be based on the relativelocations of the A/V doorbells associated with the different users. Moreparticularly, a given user (USER X) may receive a notification of theshared video footage if the shared video footage was recorded by one ofthe A/V doorbells that is located within a predetermined distance ofUSER X's own A/V doorbell. Further, in certain embodiments thepredetermined distance may be configurable by USER X. Example processesfor such sharing of recorded video footage are described below withreference to FIGS. 17-19.

FIG. 17 illustrates a neighborhood 516 comprising a plurality ofbuildings 518, such as homes, offices, retail businesses, warehouses,etc. At least some of the buildings 518 include A/V recording andcommunication doorbells secured to an exterior surface, such as adjacentthe front door. For example, FIG. 17 illustrates three A/V doorbells(A/V Doorbell #1 520, A/V Doorbell #2 522, A/V Doorbell #3 524)associated with three different buildings. Each of the A/V doorbells520, 522, 524 has a defined area around it represented by the threeoverlapping circles (Area #1 526, Area #2 528, Area #3 530). Each circle526, 528, 530 represents the area from which the owner/user of the A/Vdoorbell at the center of the circle will receive notifications ofshared video footage recorded by other A/V doorbells within the area.

For example, if A/V Doorbell #1 520 records video footage and theowner/user of A/V Doorbell #1 520 shares the recorded video footage,then the owner/user of A/V Doorbell #3 524 will receive a notificationof the shared video footage because A/V Doorbell #1 520 is locatedwithin Area #3 530, but the owner/user of A/V Doorbell #2 522 will notreceive a notification of the shared video footage because A/V Doorbell#1 520 is located outside of Area #2 528. In another example, if A/VDoorbell #2 522 records video footage and the owner/user of A/V Doorbell#2 522 shares the recorded video footage, then the owners/users of A/VDoorbells 1 and 3 will both receive a notification of the shared videofootage because A/V Doorbell #2 522 is located within both Area #1 526and Area #3 530. In another example, if A/V Doorbell #3 524 recordsvideo footage and the owner/user of A/V Doorbell #3 524 shares therecorded video footage, then neither of the owners/users of A/VDoorbells 1 and 2 will receive a notification of the shared videofootage because A/V Doorbell #3 524 is located outside of both Area #1526 and Area #2 528. The determinations of which owners/users willreceive share notifications, and which owners/users will not receiveshare notifications, are summarized in the table at the bottom of FIG.17.

FIG. 18 is a sequence diagram illustrating a process for sharing videofootage from an A/V recording and communication doorbell (or other A/Vrecording and communication device) according to an aspect of thepresent disclosure. An A/V doorbell 520 (A/V Doorbell #1, FIGS. 17 and18) may record video footage, which may also include audio. For example,the doorbell 520 may begin recording the video footage when a visitor isdetected at the doorbell 520, which may occur, for example, when thedoorbell 520 detects motion or when the visitor presses the front buttonon the doorbell 520. With further reference to FIG. 18, the doorbell 520sends a first alert signal and a first video signal 540 to the network542, and the network 542 receives the first alert signal and the firstvideo signal 540. The network 542 includes one or more network devices,such as, for example, one or more servers, routers, switches, storagedevices, etc. (not shown). At least some of the network devices includea processor and a memory. The first video signal includes images (thevideo footage) captured by a camera of the doorbell 520.

The network 542 transmits to a first client device 544 (User's ClientDevice #1), in response to receiving the first alert signal and thefirst video signal 540, a second alert signal and a second video signal546. The second alert signal may be, for example, a push notification. Apush notification, also called a server push notification, is thedelivery of information from a software application to a computingdevice without a specific request from the client. The second videosignal includes the images captured by the camera of the doorbell 520.The user associated with the first client device 544 may be theowner/user of the doorbell 520 (A/V Doorbell #1). The user, uponreceiving the second alert signal, may choose to answer the second alertsignal, which may, for example, open a live call between the user andthe visitor at the doorbell 520. Alternatively, the user may ignore thesecond alert signal (e.g. choose not to answer the call). If the userignores the second alert signal, he or she may still view the videofootage of the second video signal at a later time.

After viewing (or while viewing) the video footage on the display of hisor her client device 544, the user may decide to share the video footagewith other users. For example, the user may tap a “share” button fromwithin an application executing on his or her client device 544. Thefirst client device 544 then sends a share signal 548 to the network542, and the network 542 receives the share signal 548 from the firstclient device 544. In response to receiving the share signal 548 fromthe first client device 544, at least one of the network devices in thenetwork 542 determines the other users who are to receive a notificationof the shared video footage. For example, the network device(s) maydetermine that the doorbell 520 that recorded the shared video footageis within a predefined distance from at least one other A/V recordingand communication doorbell (or other A/V recording and communicationdevice) from among a plurality of other A/V recording and communicationdoorbells (or other A/V recording and communication devices). Forexample, with reference to FIG. 17, if the doorbell that recorded theshared video footage is A/V Doorbell #1 520, then the network device(s)may identify at least one other doorbell, such as A/V Doorbell #3 524,having a defined area (Area #3 530) around it that encompasses thelocation of the doorbell 520 that recorded the shared video footage.Once the other doorbell(s) has/have been identified, the networkdevice(s) may transmit a share notification signal 550 to each clientdevice associated with the other doorbell(s) identified (including atleast User's Client Device #3 552). The share notification signal 550may be, for example, a push notification. The other user(s), uponreceiving the share notification signal 550, may choose to view theshared video footage. Alternatively, the other user(s) may ignore theshare notification signal 550. If the other user(s) ignores the sharenotification signal 550, he or she may still view the shared videofootage at a later time.

The process described above with reference to FIG. 18 advantageouslyenables users of A/V recording and communication devices to share videofootage with one another. This feature can help reduce crime byincreasing public awareness of suspicious activity. For example, a firstuser may view video footage that was recorded by his or her doorbell anddetermine that the person or persons in the video footage are, or maybe, engaged in criminal activity. The first user may then share thatvideo footage with other users who, after viewing the shared videofootage, may be alerted to be on the lookout for the person or personsin the shared video footage and, if one or more such other users observethe person or persons in the shared video footage engaged in furthersuspicious activity, they may be more likely to report the person orpersons to law enforcement.

In the process of FIG. 18, as well as in other processes describedherein, a determination is made as to which other users will receive anotification of the video footage that is shared by the first user. Thisdetermination is based on the relative locations of the A/V recordingand communication devices associated with each of the users. And, asdescribed above with reference to FIG. 17, whether or not a given user(User X) will receive a share notification is dependent upon thedistance (alert radius) set by User X with respect to his or her own A/Vrecording and communication device(s). If the device that recorded theshared video is located within the area(s) defined by User X around hisor her own A/V recording and communication device(s), then User X willreceive a share notification. If the device that recorded the sharedvideo is located outside the area(s) defined by User X around his or herown A/V recording and communication device(s), then User X will notreceive a share notification. Thus, the determination of which userswill receive a share notification is not dependent upon an alert radiusset by the owner/user of the A/V recording and communication device thatrecorded the shared video. Rather, that determination is based on thealert radii set by the owners/users of the A/V recording andcommunication devices other than the device that recorded the sharedvideo, and many of these alert radii may differ from one another. Thatis, User X₁ may set an alert radius of one-half mile around his or herdoorbell while User X₂ may set an alert radius of three miles around hisor her doorbell. If the device that recorded the shared video is withinone-half mile of User X₁'s doorbell, then User X₁ will receive a sharenotification, and if the device that recorded the shared video is withinthree miles of User X₂'s doorbell, then User X₂ will receive a sharenotification.

Further, in some instances a first user may not receive a sharenotification while a second user may receive a share notification, eventhough the first user's doorbell is located closer to the doorbell thatrecorded the shared video than the second user's doorbell is. Forexample, again assume that User X₁ has set an alert radius of one-halfmile around his or her doorbell while User X₂ has set an alert radius ofthree miles around his or her doorbell. If User X₁'s doorbell is onemile away from the doorbell that recorded the shared video and User X₂'sdoorbell is two miles away from the doorbell that recorded the sharedvideo, then User X₁ will not receive a share notification because thedoorbell that recorded the shared video is outside User X₁'s alertradius, but User X₂ will receive a share notification because thedoorbell that recorded the shared video is inside User X₂'s alertradius.

Still further, a given user may have more than one A/V recording andcommunication device, and at least two of those devices may be indifferent locations (e.g. not on the same property or attached to thesame structure). In such cases, each device may have its own alertradius, and therefore its own defined distance/area for receiving sharenotifications. Thus, a user may receive a share notification when thedevice that recorded the shared video is within the defined area aroundat least one of that user's devices, even if the device that recordedthe shared video is outside the defined area around at least one otherof that same user's devices.

In some embodiments, a user may have more than one A/V recording andcommunication device at the same location (e.g. attached to the samestructure, or attached to separate structures that are located on thesame property). In such cases, devices that are proximate one anothermay share an alert area. For example, a user may have an A/V recordingand communication doorbell located near his or her front door and an A/Vrecording and communication security camera located at the rear of hisor her home. These devices may share one alert radius/alert area.

Still further, users may adjust as desired the size of the definedarea(s) around their A/V recording and communication device(s).Information about each A/V recording and communication device in a givenset of A/V recording and communication devices may be stored in one ormore data structures and accessed when needed to determine which userswill receive a share notification whenever a first user shares recordedvideo footage. When a user adjusts the size of the defined area(s)around his or her A/V recording and communication device(s), theinformation stored in the data structure(s) may be updated accordingly.

FIG. 19 is a flowchart illustrating another process for sharing videofootage from an A/V recording and communication doorbell (or other A/Vrecording and communication device) according to an aspect of thepresent disclosure. The process of FIG. 19 is described from theperspective of the network device(s). Thus, at block B560 the networkdevice(s) receive a first alert signal and a first video signal from afirst A/V doorbell. At block B562, the network device(s) transmit asecond alert signal and a second video signal to the first clientdevice. At block B564, the network device(s) receive a share signal fromthe first client device. At block B566, the network device(s) determineat least one second A/V doorbell within at least one predefined distancefrom the first A/V doorbell. At block B568, the network device(s)transmit a share notification signal to the at least one second clientdevice corresponding to the at least one determined second A/V doorbell.

FIGS. 20-24 are screenshots of a graphical user interface (GUI) 570illustrating aspects of a process for sharing video footage from an A/Vrecording and communication device according to an aspect of the presentdisclosure. The process of FIGS. 20-24 is described from the perspectiveof a user who receives an alert signal and a video signal on his or herclient device. Thus, the GUI 570 illustrated in FIGS. 20-24 isconfigured to be displayed on a display of the user's client device,such as a smartphone.

With reference to FIG. 20, a live call screen 572 is illustrated. When auser's A/V recording and communication device detects motion, or, in thecase of a doorbell, when a visitor presses the front button on thedoorbell, the user receives an alert on his or her client device alongwith streaming video footage recorded by the camera of the A/V recordingand communication device. If the user answers the alert, a live callscreen 572 such as that shown in FIG. 20 may be displayed on the user'sclient device. The live call screen 572 may include one or more buttons,such as an END button 574 (to terminate or disconnect the call), avolume adjust button 576, a mute button 578, a full screen button 580(to expand the video so that it fills the entire display screen), and/ora menu button 582.

The live call screen 572 may further include a neighborhood share button584. If the user selects the neighborhood share button 584 during thelive call, the GUI 570 may display a notification 586 that the user willbe prompted after the live call to share the video of the call withother users in the user's “neighborhood,” e.g. those users determinedaccording to the process described above with reference to FIGS. 18 and19. For example, as shown in FIG. 21, the notification 586 may appear ina banner portion 588 of the live call screen 572. Advantageously,displaying the notification 586 in a banner 588 does not interrupt thelive call, so that the user and the visitor can continue speaking to oneanother for as long as desired.

If the user selects the neighborhood share button 584 during the livecall, then after the call is terminated, such as when the user selectsthe END button 574 on the live call screen 572 (FIG. 20), a shareinformation screen 590 may be shown on the GUI 570, as shown in FIG. 22.In the illustrated embodiment, the share information screen 590 includesa still image 592 from the video that was recorded during the live call,and textual information 594. For example, the text 594 may include aphrase such as “Alert your neighborhood,” which informs (or reminds) theuser that he or she is about to share the recorded video footage withone or more other users. The text 594 may further include a notice thatthe video footage will be shared along with a general indication ofwhere the video was recorded. For example, the location information mayidentify the street name and block number, such as “1300 block of14^(th) Street,” and/or may identify the nearest intersection, such as“Near the intersection of 14^(th) Street and Santa Monica Boulevard.” Anicon 596, such as a question mark, may also be displayed. If the userselects the question mark icon 596, further information about the sharefeature may be displayed, and/or a help menu may be displayed.

The share information screen 590 may further include a text entry box598. If the user selects the text entry box 598, such as by tapping onit if the user's client device includes a touchscreen display, akeyboard 600 may appear on the display, as shown in FIG. 23. The usermay then enter text to describe the content of the shared video. Afterentering text, the user may select a SHARE button 602, after which theshare signal (FIG. 18) is sent to the network and the network identifiesone or more other users who will be notified of the shared video andsends out notifications to the identified other users. The share signalmay include, or be accompanied by, the text entered by the user in thetext entry box 598 of the GUI 570 shown in FIG. 23. The user may alsodecline to enter any text in the text entry box 598, and may insteadsimply select the SHARE button 602 from the share information screen 590of FIG. 22, after which the share signal (FIG. 18) is sent to thenetwork and the network identifies one or more other users who will benotified of the shared video and sends out notifications to theidentified other users.

After the user selects the SHARE button 602, with or without enteringtext in the text entry box 598, a confirmation screen 604 may bedisplayed on the display of the user's client device, as shown in FIG.24. The confirmation screen 604 may include text 606, such as a messageconfirming that the video has been shared (“Your video has been shared”)and/or a thank you message (“Thanks for helping to keep yourneighborhood safe.”). The confirmation screen 604 may further include abutton, such as an OK button 608, which, when selected, may return theuser to another screen, such as a menu screen, of the applicationexecuting on the user's client device. With reference to FIGS. 22-24,the share information screen 590 (FIG. 22), the text entry screen 610(FIG. 23), and/or the confirmation screen 604 (FIG. 24) may include aclose button 612 (the “X” in the upper right-hand corner). If the userselects the close button 612, the share operation may be terminatedwithout sharing the video footage from the live call. Further, if theuser selects the close button 612, a popup window (not shown) may beshown on the display asking the user to confirm that the share operationis to be terminated.

In further reference to FIGS. 20-24, in some embodiments the sharesignal may be sent to the network, and the network may enable one ormore of the identified recipient users to further comment about theshared video and/or the text regarding the shared video. In someembodiments, the further comments may be directed to the user thatshared the video, or may be directed to all the users. For example, if auser shares a video depicting a person committing a crime, another userthat receives the shared video may recognize the person depicted in thevideo (the perpetrator). The recipient user may then send identifyinginformation about the perpetrator, which may be useful in apprehendingthe perpetrator. In some embodiments, the identifying information may besent directly to the user that shared the information, or it may beposted to the network such that it is visible to all the recipients ofthe shared video. In another example, if a user shares a video depictinga person committing a crime, and knows (or recognizes) the perpetrator,then users that receive the shared video may request the identifyinginformation about the person directly from the user that shared thevideo. In some embodiments, the user that shared the video may get adirect message such as (but not limited to) an email requesting theinformation. The user may then decide whether or not to provide theidentifying information to the requesting user. A further example mayinclude the network providing a comment section with the shared video sothat the various users may provide comments regarding the shared video.An additional example may include allowing users to post comments and/orsend messages regarding the shared video without revealing theirpersonal identity and/or contact information, such as email addresses.In further embodiments, the share signal may include image data and/oraudio data that is captured and transmitted to the network in real-time(or near real-time), which may make the share signal a live video feed.In such embodiments, a user may set his or her share features toautomatically share particular events and/or types of events to thenetwork. In some embodiments, various users may comment on the sharedlive video feed, as described above.

FIGS. 25-29 are screenshots of a graphical user interface (GUI) 620illustrating aspects of another process for sharing video footage froman A/V recording and communication device according to an aspect of thepresent disclosure. The process of FIGS. 25-29 is described from theperspective of a user who views an earlier-recorded video on his or herclient device. Thus, the GUI 620 illustrated in FIGS. 25-29 isconfigured to be displayed on a display of the user's client device,such as a smartphone. In this embodiment, the video displayed on theuser's client device is not a live call, but rather is a recording of avisitor event that took place earlier in time. The recording may be,however, a recording of an earlier live call between the user and thevisitor.

With reference to FIG. 25, a video playback screen 622 is illustrated.When a user's A/V recording and communication device detects motion, or,in the case of a doorbell, when a visitor presses the front button onthe doorbell, the user receives an alert on his or her client devicealong with streaming video footage recorded by the camera of the A/Vrecording and communication device. If the user ignores the alert, themotion event or button press event may nevertheless be recorded andstored at a remote network device. When the user later accesses thestored video footage, the video may be displayed on the video playbackscreen 622 on the user's client device, as shown in FIG. 25.Alternatively, if the user answers the alert and communicates with thevisitor but does not share the video from within the live call (asdescribed above with respect to FIGS. 20-24), the user may still viewthe recorded video footage by accessing it from a menu, as describedbelow.

With further reference to FIG. 25, the video playback screen 622 mayinclude one or more buttons or controls, such as a volume adjustmentslider widget 624, a rewind button 626, a play button 628, a fastforward button 630, a delete button 632, and/or a share button 634. Ifthe user selects the share button 634, a popup menu (not shown) may beshown on the display offering the user one or more options for sharingthe video with his or her contacts and/or via social media. For example,the popup menu (or any other suitable type of interface) may includeoptions for sharing the video via e-mail, via text message, and/or viasocial media, such as on NEXTDOOR®, FACEBOOK®, INSTAGRAM®, TWITTER®,etc. When the user selects one of the options, a new message (or post,etc.) may then be created including a link to the video to be shared.For example, if the user selects a social media network through which toshare the video, the process may create a social media post with a linkto the video to be shared. Posting the video to one or more socialnetworks may enable the video to be seen by others, including others wholive in the neighborhood where the video was recorded. Those persons mayrecognize a person in the video, and may be able to help identify thatperson. Further, the social network post may provide a warning to otherswho live in the neighborhood where the video was recorded, encouragingthose people to be watchful for the person(s) in the video.

While the present embodiments are not limited to use with any particularsocial network, or type of social network, the present embodiments maynevertheless be well adapted for use with a neighborhood-oriented socialnetwork, such as NEXTDOOR®. Neighborhood-oriented social networks allowusers to connect with people who live in their neighborhood, and/or innearby neighborhoods, by limiting access to posts to the people in thesame neighborhood as the poster, or those nearby. As described above, insome aspects the present embodiments enable a user to share a video to asocial network. When the video is posted to a social networking servicefor neighborhoods, the video is more likely to be seen by people wholive in the neighborhood where the video was recorded. The video is thusmore likely to be relevant to the people in the neighborhood-orientedsocial network, because those people are more likely to have also seenthe person(s) in the video. The neighborhood-oriented social networkmembers may therefore be able to provide additional information aboutthe person(s) in the video, such as confirming that they too have seenthe person(s) in the neighborhood and/or helping to identify theperson(s) in the video. If the person(s) in the video has committedcriminal acts in the neighborhood, identifying the person(s) may helplead to their capture and conviction.

With further reference to FIG. 25, the video playback screen 622 mayfurther include a progress bar 636 and a slider widget 638 thatindicates what portion of the video is currently playing. For example, atimer 640 at a first end 642 of the progress bar 636 indicates how muchof the video has elapsed, and a timer 644 at a second end 646 of theprogress bar 636 indicates how much of the video is left to play. As thevideo plays, the progress slider widget 638 moves from the first end 642to the second end 646 of the progress bar 636. If the user wants to jumpto a particular portion of the video, he or she may move the sliderwidget 638 left or right by selecting it, sliding it along the progressbar 636, and releasing it. The video playback screen 622 may furtherinclude a Done button 648, which, when selected, closes the video andreturns the user to a previous screen within the application executingon the user's client device.

With further reference to FIG. 25, the video playback screen 622 mayfurther include a neighborhood share button 584. If the user selects theneighborhood share button 584, the GUI 620 may display textualinformation 594, as shown in FIG. 26. For example, the text 594 mayinclude a phrase such as “Alert your neighborhood,” which informs (orreminds) the user that he or she is about to share the recorded videofootage with one or more other users. The text 594 may further include anotice that the video footage will be shared along with a generalindication of where the video was recorded. For example, the locationinformation may identify the street name and block number, such as “1300block of 14^(th) Street,” and/or may identify the nearest intersection,such as “Near the intersection of 14^(th) Street and Santa MonicaBoulevard.” An icon 596, such as a question mark, may also be displayed.If the user selects the question mark icon 596, further informationabout the share feature may be displayed, and/or a help menu may bedisplayed.

The GUI 620 of FIG. 26 may further include a text entry box 598. If theuser selects the text entry box 598, such as by tapping on it if theuser's client device includes a touchscreen display, a keyboard 600 mayappear on the display, as shown in FIG. 27. The user may then enter textto describe the content of the shared video. After entering text, theuser may select a SHARE button 602, after which the share signal (FIG.18) is sent to the network and the network identifies one or more otherusers who will be notified of the shared video and sends outnotifications to the identified other users. The share signal mayinclude, or be accompanied by, the text entered by the user in the textentry box 598 of the GUI 620 shown in FIG. 27. The user may also declineto enter any text in the text entry box 598, and may instead simplyselect the SHARE button 602 from the share screen 650 of FIG. 26, afterwhich the share signal (FIG. 18) is sent to the network and the networkidentifies one or more other users who will be notified of the sharedvideo and sends out notifications to the identified other users.

After the user selects the SHARE button 602, with or without enteringtext in the text entry box 598, a confirmation message 652 may bedisplayed on the GUI 620 of the user's client device, as shown in FIG.28. The confirmation message 652 may include text, such as a messageconfirming that the video has been shared (“Your video has been postedand your neighborhood has been alerted.”). With reference to FIG. 29, apopup message 654 may also be shown asking the user if he or she wouldlike to “unshare” the video. The popup message 654 may include text 656such as “You have already shared this video with your Neighborhood.” andone or more buttons, such as a CANCEL button 658 and/or a YES (or OK)button 660. If the user selects the YES button 660, the shared video maybe “unshared,” whereas if the user selects the CANCEL button 658, theshared video will not be “unshared.” With reference to FIGS. 26-28, theGUI 620 may include a close button 612 (the “X” in the upper right-handcorner). If the user selects the close button 612, the share operationmay be terminated without sharing the video footage. Further, if theuser selects the close button 612, a popup window (not shown) may beshown on the display asking the user to confirm that the share operationis to be terminated.

In some embodiments, video footage recorded by a user's A/V recordingand communication device may not be stored at a remote network device ona long-term basis. In such embodiments, the user may still share videofootage from his or her A/V recording and communication device withother users, but only from a live call, such as according to the processdescribed above with reference to FIGS. 20-24 (and not from a videoplayback process, such as that described above with reference to FIGS.25-29). To enable this aspect, all video recorded by the user's A/Vrecording and communication device may be temporarily stored at a remotenetwork device so that it is available for sharing if the user sharesthe video footage from the live call. For example, the video may betemporarily stored at a remote network device as long as the live callis in progress, but if the live call terminates without the userselecting the neighborhood share button 584 (FIG. 20), the video thatwas temporarily stored at the remote network device may then be deleted.

In further reference to FIGS. 25-29, and as described above with respectto FIGS. 20-24, in some embodiments, the share signal may be sent to thenetwork, and the network may enable one or more of the identifiedrecipient users to further comment about the shared video and/or thetext regarding the shared video. In some embodiments, the furthercomments may be directed to the user that shared the video, or may bedirected to all the users. For example, if a user shares a videodepicting a person committing a crime, another user that receives theshared video may recognize the person depicted in the video (theperpetrator). The recipient user may then send identifying informationabout the person, which may be useful in apprehending the perpetrator.In some embodiments, the identifying information may be sent directly tothe user that shared the information, or it may be posted to the networksuch that it is visible to all the recipients of the shared video. Inanother example, if a user shares a video depicting a person committinga crime, and knows (or recognizes) the perpetrator, then users thatreceive the shared video may request the identifying information aboutthe person directly from the user that shared the video. In someembodiments, the user that shared the video may get a direct messagesuch as (but not limited to) an email requesting the information. Theuser may then decide whether or not to provide the identifyinginformation to the requesting user. A further example may include thenetwork providing a comment section with the shared video so that thevarious users may provide comments regarding the shared video. Anadditional example may include allowing users to post comments and/orsend messages regarding the shared video without revealing theirpersonal identity and/or contact information, such as email addresses.In further embodiments, the share signal may include image data and/oraudio data that is captured and transmitted to the network in real-time(or near real-time) which may make the share signal a live video feed.In such embodiments, a user may set his or her share features toautomatically share particular events and/or types of events to thenetwork. In some embodiments, various users may comment on the sharedlive video feed, as described above.

FIG. 30 is a sequence diagram illustrating another process for sharingvideo footage from an A/V recording and communication doorbell accordingto an aspect of the present disclosure. The process of FIG. 30 includesaspects of the process of FIG. 18, including the doorbell 520 sending afirst alert signal and a first video signal 540 to the network (and thenetwork receives the first alert signal and the first video signal 540),the network 542 transmitting to a first client device (User's ClientDevice #1), in response to receiving the first alert signal and thefirst video signal, a second alert signal and a second video signal 546,the first client device 544 sending a share signal 548 to the network(and the network receiving the share signal 548 from the first clientdevice), and the network device(s) 542 transmitting a share notificationsignal 550 to each client device associated with the other doorbell(s)identified (including at least User's Client Device #3 552).

The process of FIG. 30 further comprises the third client device 552sending a playback request signal 662 to the network 542 (and thenetwork 542 receiving the playback request signal 662 from the thirdclient device 552), and the network device(s) 542, in response toreceiving the playback request signal 662 from the third client device552, transmitting a third video signal 664 to the third client device552, the third video signal 664 including the shared video footagerecorded by A/V Doorbell #1 520. For example, User's Client Device #3552 may receive the share notification signal 550, which may be, forexample, a push notification. The user associated with User's ClientDevice #3 552 may then choose to view the shared video footage, such asby selecting a “VIEW NOW” button (or an “OK” button, etc.) in the pushnotification. Alternatively, the user may ignore the share notificationsignal 550, but may subsequently request to view the shared videofootage through one or more screens/menus within an applicationexecuting on User's Client Device #3 552, as described below. Theplayback request signal 662 is then sent to the network 542, and theshared video footage is sent to User's Client Device #3 552 in the thirdvideo signal 664.

FIG. 31 is a flowchart illustrating another process for sharing videofootage from an A/V recording and communication doorbell according to anaspect of the present disclosure. The process of FIG. 31 is describedfrom the perspective of the network device(s). Thus, at block B560 thenetwork device(s) receive a first alert signal and a first video signalfrom a first A/V doorbell. At block B562, the network device(s) transmita second alert signal and a second video signal to the first clientdevice. At block B564, the network device(s) receive a share signal fromthe first client device. At block B566, the network device(s) determineat least one second A/V doorbell within at least one predefined distancefrom the first A/V doorbell. At block B568, the network device(s)transmit a share notification signal to the at least one second clientdevice corresponding to the at least one determined second A/V doorbell.At block B670, the network device(s) receive a playback request signalfrom the second client device. At block B672, the network device(s)transmits a third video signal to the second client device.

FIGS. 32-35 are screenshots of graphical user interfaces (GUIs)illustrating aspects of another process for sharing video footage froman A/V recording and communication device according to an aspect of thepresent disclosure. FIGS. 32-35 are described below from the perspectiveof a user operating his or her client device. Thus, the GUIs illustratedin FIGS. 32-35 are configured to be displayed on a display of the user'sclient device, such as a smartphone.

With reference to FIG. 32, the GUI 680 includes buttons for each of theuser's A/V recording and communication devices. For example, the GUI 680of FIG. 32 includes a first button 682 for the doorbell located adjacentthe user's front door and a second button 684 for the doorbell locatedadjacent the user's back door. The user may view video footage recordedby his or her devices by selecting from among the buttons 682, 684corresponding to each device. The user may further view video footageorganized by type by selecting from among a plurality of filter buttons686, 688, 690. For example, the GUI 680 of FIG. 32 includes a firstfilter button 686 for ALL ACTIVITY, a second filter button 688 for CALLS(video recorded when the front button on the user's doorbell ispressed), and a third filter button 690 for MOTION (video recorded whenthe user's doorbell detects motion). When the user selects the ALLACTIVITY filter button 686, a list 691 may be displayed on the GUI 680that includes entries for all videos recorded by the user's device(s),as well as entries for all shared videos recorded by other users'devices in the user's “neighborhood,” e.g. those devices determinedaccording to the process described above with reference to FIGS. 18 and19. For example, the list 691 of FIG. 32 includes entries labeled“ACCEPTED RING” 692 and “MISSED RING” 694, which correspond to videosrecorded by the user's doorbell(s) in response to the button on thedoorbell(s) being pressed. The list 691 further includes entries labeled“MISSED MOTION” 696, which correspond to videos recorded by the user'sdevice(s) in response to motion being detected.

The list 691 of FIG. 32 further includes an entry labeled “NEIGHBORHOODALERT [Suspicious Activity]” 698. The neighborhood alert entry 698 mayfurther include a neighborhood event icon 700, which identifies theentry 698 as corresponding to a shared video from another user's devicein the user's “neighborhood.” The neighborhood alert entry 698 mayfurther include information about the shared video, including theapproximate location 702 where it was recorded, the day and time 704when it was recorded, and a textual description 706 of the video asprovided by the user whose device recorded the video. If the userselects the neighborhood alert entry 698, a playback request signal 662is sent from the user's client device to the network (FIG. 30), and avideo signal 664 including the requested video is sent from the networkto the user's client device. A GUI similar to that shown in FIG. 25 (butwithout the neighborhood share button) may then be shown on the displayof the user's client device and the user may view the shared video.

With reference to FIG. 33, the GUI 680 may further include a side menu708. The side menu 708 may be accessed, for example, by touching thedisplay of the user's client device and swiping to the right (if thedisplay of the user's client device is a touchscreen). The side menu 708may include buttons 710 for various settings, buttons 712 for each ofthe user's A/V recording and communication devices, as well as aNEIGHBORHOOD button 714. The NEIGHBORHOOD button 714 may further includethe neighborhood event icon 700, which is described in the foregoingparagraph. When the user selects the NEIGHBORHOOD button 714, theNEIGHBORHOOD ACTIVITY screen 716 illustrated in FIG. 34 may be displayedon the display of the user's client device.

With reference to FIG. 34, the NEIGHBORHOOD ACTIVITY screen 716 mayinclude a Neighborhood button 718 and an Alert Settings button 720. Whenthe user selects the Neighborhood button 718, a NEIGHBORHOOD ACTIVITYlist 722 may be displayed on the GUI 680 that includes neighborhoodalert entries 698 (the content and functionality of which is describedabove with respect to FIG. 32). With further reference to FIG. 34, whenthe user selects the Alert Settings button 720, if the user has A/Vrecording and communication devices at more than one location, then aSelect a Neighborhood screen 724 may be displayed on the display of theuser's client device, as shown in FIG. 35. The Select a Neighborhoodscreen 724 may include a list 726 having entries corresponding to eachlocation (e.g. each “neighborhood”) where the user has at least one A/Vrecording and communication device. For example, the list 726 of FIG. 35includes a first entry 728 for the user's home “neighborhood” and asecond entry 730 for the user's office “neighborhood.” In certainembodiments, if the user has more than one A/V recording andcommunication device at a given location, only one entry may bedisplayed per location. For example, if the user has two doorbells andone security camera at a given address, only one entry appears in thelist 726 for that location, and the entry covers all three devices atthat location. If the user has one or more A/V recording andcommunication devices at another location, another entry appears in thelist 726 for that other location. Also in certain embodiments, theentries in the list 726 may comprise addresses rather than, or inaddition to, names. For example, rather than the first entry 728 beinglabeled “Home” and the second entry 730 being labeled “Office,” thefirst entry 728 may be labeled “123 Main Street” and the second entry730 may be labeled “456 First Street.”

If, however, the user does not have A/V recording and communicationdevices at more than one location, then when the user selects the AlertSettings button 720 (FIG. 34) a Neighborhood Alert Settings screen 732may be displayed on the display of the user's client device, as shown inFIGS. 36 and 37. Further, if the user has A/V recording andcommunication devices at more than one location, then when the userselects one of the locations from the list 726 on the NEIGHBORHOODACTIVITY screen 716 of FIG. 35, then the Neighborhood Alert Settingsscreen 732 of FIGS. 36 and 37 may also be displayed on the display ofthe user's client device.

With reference to FIG. 36, the Neighborhood Alert Settings screen 732includes an ON/OFF slider widget 734 that enables the user to toggle thevideo sharing feature on and off. When the ON/OFF slider widget 734 isin the ON position, as shown in FIG. 36, the user may receive sharingnotifications (alerts) when other users in the user's “neighborhood”share videos, and shared videos may appear in the list 691 of events onthe user's ALL ACTIVITY screen 736 (FIG. 32), as well as in the list 722of events on the user's NEIGHBORHOOD ACTIVITY screen 716 (FIG. 34). Incertain embodiments, the ON/OFF slider widget 734 may be in the ONposition by default. When the ON/OFF slider widget 734 is in the OFFposition, as shown in FIG. 37, the user may not receive sharingnotifications (alerts) when other users in the user's “neighborhood”share videos, and shared videos may not appear in the list 691 of eventson the user's ALL ACTIVITY screen 736 (FIG. 32), but shared videos mayappear in the list 722 of events on the user's NEIGHBORHOOD ACTIVITYscreen 716 (FIG. 34). The Neighborhood Alert Settings screen 732 furtherincludes a text banner 738 that explains how the video sharing featurefunctions when the ON/OFF slider widget 734 is in the ON position (FIG.36) and when the ON/OFF slider widget 734 is in the OFF position (FIG.37).

With reference to FIG. 36, the Neighborhood Alert Settings screen 732further includes a map 740. An indicator 742 on the map 740 indicatesthe location of the user's A/V recording and communication device(s)corresponding to the location selected from the list 724 of FIG. 35 (orcorresponding to the single location at which the user has at least oneA/V recording and communication device, if the user does not have A/Vrecording and communication devices at more than one location). In theillustrated embodiment, the indicator 742 comprises a dot, but in otherembodiments the indicator 742 may comprise any other type of indicator,such as a pin, for example. The Neighborhood Alert Settings screen 732further includes a text banner 744 that provides the street address ofthe location corresponding to the indicator 742 on the map 740.

With further reference to FIG. 36, the Neighborhood Alert Settingsscreen 732 further includes a slider widget 746 for adjusting the alertradius around the user's A/V recording and communication device(s) atthe location indicated on the map 740. A circle 748 around the indicator742 on the map 740 identifies the outer boundary of the area 750 fromwhich the user will receive share notifications from other users. Anarea 750 within the circle 748 may be shaded, as indicated in FIG. 36.To adjust the size of the area 750, the user adjusts the length of thealert radius by moving the slider widget 746 up or down. In theillustrated embodiment, moving the slider widget 746 up increases thesize of the area 750 (and the alert radius), while moving the sliderwidget 746 down decreases the size of the area 750 (and the alertradius). As the slider widget 746 is moved up and down, the size of thecircle 748 around the indicator 742 may increase and decrease to providethe user with a visual representation of the area 750 covered as thelength of the alert radius increases and decreases. In some embodiments,the map 740 may have a default scale. As the user moves the sliderwidget 746 up to increase the size of the alert radius, if the circle748 reaches the edges of the map 740, then the map 740 may begin toscale down so that the entire alert area 750 is always visible on themap 740.

When the user adjusts the size of the alert radius, the user's clientdevice may send an alert radius adjustment signal to the network and thenetwork may update a data structure with the changed size of the user'salert radius. For example, with further reference to FIG. 36, the usermay adjust the size of the alert radius by moving the slider widget 746up or down. To confirm the change, the user may select a back arrow 752on the GUI 680 to return to the previous screen within the applicationexecuting on the user's client device. When the user selects the backarrow 752, the alert radius adjustment signal is sent to the network andthe network updates the data structure with the changed size of theuser's alert radius. In some embodiments, if the user exits theapplication without selecting the back arrow 752, then the adjustment ofthe alert radius may be discarded (the size of the alert radius mayremain unchanged).

With further reference to FIG. 36, the magnitude of the alert radius maybe indicated by a number on the slider widget 746. For example, in FIG.36 the alert radius is set at 0.2 miles, as indicated by the number 0.2on the slider widget 746. Maximum and/or minimum magnitudes of the alertradius may be indicated by numbers at opposite ends of the slider widget746. For example, in FIG. 36 the maximum alert radius is indicated as 10miles at the upper end of the slider widget 746, while the minimum alertradius is indicated as 0.1 miles at the lower end of the slider widget746. It should be appreciated that the maximum and minimum magnitudesshown in FIGS. 36 and 37 are just examples and are not limiting.

In certain embodiments, the magnitude of the alert radius may bedynamically set based on the number of other A/V recording andcommunication devices around the location indicated on the map 740. Forexample, the alert radius may be set such that the resulting definedarea 750 around the user's A/V recording and communication deviceencompasses at least a minimum threshold number of other A/V recordingand communication devices. Alternatively, the alert radius may be setsuch that the resulting defined area 750 around the user's A/V recordingand communication device encompasses no more than a maximum thresholdnumber of other A/V recording and communication devices. Still further,the alert radius may be set such that the resulting defined area 750around the user's A/V recording and communication device encompasses anumber of other A/V recording and communication devices that fallswithin a defined range. In certain embodiments, the magnitude of thealert radius may be dynamically adjusted as the number of other A/Vrecording and communication devices around the user's device changes.Thus, as more A/V recording and communication devices are added aroundthe user's device, the size of the alert radius may be decreased so thatthe number of other A/V recording and communication devices in thedefined area 750 remains about the same. Conversely, as A/V recordingand communication devices are removed (or deactivated) from the area 750around the user's device, the size of the alert radius may be increasedso that the number of other A/V recording and communication devices inthe defined area 750 remains about the same. In certain embodiments, theuser may override the dynamic setting and/or adjustment of the magnitudeof the alert radius by manually selecting the magnitude of the alertradius by moving the slider widget 746 as described above with referenceto FIG. 36.

In some embodiments, the defined alert area about a user's A/V recordingand communication device may not have a circular outer boundary. Forexample, a user may define an alert area about his or her A/V recordingand communication device that has a non-circular shape, such as square,rectangular, or any other shape, including irregular polygons. The shapeof the alert area may also extend a greater distance from A/V recordingand communication device in one direction than in another direction. Forexample, if an A/V recording and communication device is located in acoastal area, or on a lakefront, or on an edge of an uninhabited area(such as a desert), or on an edge of a restricted area (such as amilitary base), then the user may not want the alert area to extend overthe water, or desert, or military base, etc., but the user may want thealert area to extend a substantial distance in directions away from thewater, or desert, or military base, etc. In such embodiments, the A/Vrecording and communication device would not be located at the center ofthe defined alert area.

FIG. 38 is a sequence diagram illustrating another process for sharingvideo footage from an A/V recording and communication doorbell accordingto an aspect of the present disclosure. In the process of FIG. 38, a newA/V recording and communication device is activated and connected to thenetwork. In certain embodiments, some aspects of theactivation/setup/connection process may be carried out using anapplication executing on the user's client device. Thus, with referenceto FIG. 38, the user's client device 754 (User's Client Device #1) maysend to the network 756, and the network 756 may receive from the user'sclient device 754, information 758 associated with the user's A/Vrecording and communication device (A/V Doorbell #1). The information758 may include, for example, the location of the user's A/V recordingand communication device. The location may comprise the street addressof a building with which the user's A/V recording and communicationdevice is associated, such as being secured thereto, for example. Theuser's client device 754 may further send to the network 756, and thenetwork 756 may further receive from the user's client device 754, anenable signal 760 for the video sharing feature of the user's A/Vrecording and communication device. For example, during the setupprocess the user may enable (turn on) the video sharing feature using aGUI such as that illustrated in FIG. 36. In some embodiments, the videosharing feature may be enabled by default, such that the user does nothave to take any affirmative steps to enable the video sharing feature.

With further reference to FIG. 38, the user's client device 754 mayfurther send to the network 756, and the network 756 may further receivefrom the user's client device 754, a notification distance (alertradius) 762 associated with the video sharing feature of the user's A/Vrecording and communication device. For example, during the setupprocess the user may select an alert radius 762 using a GUI such as thatillustrated in FIG. 36. In some embodiments, the alert radius 762 may beset automatically to a default value, or may be set automaticallyaccording to the criteria described above, such that the user does nothave to take any affirmative steps to set the alert radius 762. Thealert radius 762 defines an area around the user's A/V recording andcommunication device that encompasses at least one other A/V recordingand communication device, which in this example will be referred to asA/V Doorbell #2. A/V Doorbell #2 may record video footage, and the userassociated with A/V Doorbell #2 may share the recorded video footageaccording to a process described herein. Thus, with further reference toFIG. 38, the client device associated with A/V Doorbell #2 (User'sClient Device #2 764) may send to the network 756, and the network 756may receive from User's Client Device #2 764, a share signal 766. Thenetwork 756, after determining that A/V Doorbell #2 764 is within thealert area defined around A/V Doorbell #1, may then send a sharenotification signal 768 to the client device associated with A/VDoorbell #1 (User's Client Device #1 754).

FIGS. 39 and 40 are flowcharts illustrating other processes for sharingvideo footage from an A/V recording and communication doorbell accordingto an aspect of the present disclosure. FIG. 39 is described from theperspective of the user, while FIG. 40 is described from the perspectiveof the network device(s). Thus, with reference to FIG. 39, at block B770the user may activate a new A/V recording and communication device andconnect it to the network. As described above, some aspects of theactivation/setup/connection process may be carried out using anapplication executing on the user's client device. At block B772, theuser may enable the video sharing feature of the user's A/V recordingand communication device, and at block B774 the user may set anotification distance (alert radius) associated with the video sharingfeature of the user's A/V recording and communication device. Asdescribed above, these aspects of the activation/setup/connectionprocess may be automated, such that the user does not have to take anyaffirmative steps. The alert radius defines an area around the user'sA/V recording and communication device that encompasses at least oneother A/V recording and communication device, which in this example willbe referred to as a second A/V doorbell. The second A/V doorbell mayrecord video footage, and the user associated with the second A/Vdoorbell may share the recorded video footage according to a processdescribed herein. The client device associated with the second A/Vdoorbell may send to the network, and the network may receive from thesecond A/V doorbell, a share signal. The network, after determining thatthe second A/V doorbell is within the alert area defined around A/VDoorbell #1, may then send a share notification signal to the clientdevice associated with A/V Doorbell #1 (first client device). Thus, atblock B776 the first client device may receive the share notificationsignal, including a link to the video footage recorded by the second A/Vdoorbell that is within the notification distance (alert radius) of thefirst A/V doorbell.

With reference to FIG. 40, at block B778 the network may receive fromthe user's client device information associated with the user's A/Vrecording and communication device (first A/V doorbell). The informationmay include, for example, the location of the first A/V doorbell. Thelocation may comprise the street address of a building with which thefirst A/V doorbell is associated, such as being secured thereto, forexample. At block B780, the network may further receive from the user'sclient device, an enable signal for the video sharing feature of thefirst A/V doorbell. For example, during the setup process the user mayenable (turn on) the video sharing feature using a GUI such as thatillustrated in FIG. 36. In some embodiments, the video sharing featuremay be enabled by default, such that the user does not have to take anyaffirmative steps to enable the video sharing feature.

With further reference to FIG. 40, at block B782 the network may furtherreceive from the user's client device a notification distance (alertradius) associated with the video sharing feature of the first A/Vdoorbell. For example, during the setup process the user may select analert radius using a GUI such as that illustrated in FIG. 36. In someembodiments, the alert radius may be set automatically to a defaultvalue, or may be set automatically according to the criteria describedabove, such that the user does not have to take any affirmative steps toset the alert radius. At block B784, the network may update one or moredata structures (alert areas) with the information received about thefirst A/V doorbell, including its location and/or its alert radius.

The alert radius defines an area around the first A/V doorbell thatencompasses at least one other A/V recording and communication device,which in this example will be referred to as second A/V doorbell. Thesecond A/V doorbell may record video footage, and the user associatedwith the second A/V doorbell may share the recorded video footageaccording to a process described herein. Thus, with further reference toFIG. 40, at block B786 the network may receive from the second clientdevice a share signal. The network, after determining, at block B788,that the second A/V doorbell is within the alert area defined around thefirst A/V doorbell, may then send a share notification signal to theclient device associated with the first A/V doorbell at block B790.

FIG. 41 is a sequence diagram illustrating another process for sharingvideo footage from an A/V recording and communication doorbell accordingto an aspect of the present disclosure. The process of FIG. 41 includesaspects of the process of FIG. 38, including the user's client device754 (User's Client Device #1) sending to the network 756 (and thenetwork 756 receiving from the user's client device 754, information 758associated with the user's A/V recording and communication device (A/VDoorbell #1), the user's client device 754 further sending to thenetwork 756 (and the network 756 further receiving from the user'sclient device 754) an enable signal 760 for the video sharing feature ofthe user's A/V recording and communication device, the user's clientdevice 754 further sending to the network 756 (and the network 756further receiving from the user's client device 754) a notificationdistance (alert radius) 762 associated with the video sharing feature ofthe user's A/V recording and communication device, the second clientdevice 764 (User's Client Device #2) sending a share signal 766 to thenetwork 756 (and the network 756 receiving the share signal 766 from thesecond client device 764), and the network device(s) 756 transmitting ashare notification signal 768 to the user's client device 754.

The process of FIG. 41 further comprises the user's client device 754sending a playback request signal 792 to the network 756 (and thenetwork 756 receiving the playback request signal from the user's clientdevice 754), and the network device(s) 756, in response to receiving theplayback request signal 792 from the user's client device 754,transmitting a video signal 794 to the user's client device 754, thevideo signal 794 including the shared video footage recorded by A/VDoorbell #2. For example, User's Client Device #1 754 may receive theshare notification signal 768, which may be, for example, a pushnotification. The user associated with User's Client Device #1 754 maythen choose to view the shared video footage, such as by selecting a“VIEW NOW” button (or an “OK” button, etc.) in the push notification.Alternatively, the user may ignore the share notification signal 768,but may subsequently request to view the shared video footage throughone or more screens/menus within an application executing on User'sClient Device #1 754, as described above. The playback request signal768 is then sent to the network 756, and the shared video footage issent to User's Client Device #1 754 in the video signal 794.

FIG. 42 is a flowchart illustrating another process for sharing videofootage from an A/V recording and communication doorbell according to anaspect of the present disclosure. The process of FIG. 42 is describedfrom the perspective of the network device(s). Thus, at block B778 thenetwork receives from the user's client device information associatedwith the user's A/V recording and communication device (first A/Vdoorbell). The information may include, for example, the location of thefirst A/V doorbell. The location may comprise the street address of abuilding with which the first A/V doorbell is associated, such as beingsecured thereto, for example. At block B780, the network may furtherreceive from the user's client device, an enable signal for the videosharing feature of the first A/V doorbell. For example, during the setupprocess the user may enable (turn on) the video sharing feature using aGUI such as that illustrated in FIG. 36. In some embodiments, the videosharing feature may be enabled by default, such that the user does nothave to take any affirmative steps to enable the video sharing feature.

With further reference to FIG. 42, at block B782 the network may furtherreceive from the user's client device a notification distance (alertradius) associated with the video sharing feature of the first A/Vdoorbell. For example, during the setup process the user may select analert radius using a GUI such as that illustrated in FIG. 36. In someembodiments, the alert radius may be set automatically to a defaultvalue, or may be set automatically according to the criteria describedabove, such that the user does not have to take any affirmative steps toset the alert radius. At block B784, the network may update one or moredata structures (alert areas) with the information received about thefirst A/V doorbell, including its location and/or its alert radius.

The alert radius defines an area around the first A/V doorbell thatencompasses at least one other A/V recording and communication device,which in this example will be referred to as second A/V doorbell. Thesecond A/V doorbell may record video footage, and the user associatedwith the second A/V doorbell may share the recorded video footageaccording to a process described herein. Thus, with further reference toFIG. 40, at block B786 the network may receive from the second clientdevice a share signal. The network, after determining, at block B788,that the second A/V doorbell is within the alert area defined around thefirst A/V doorbell, may then send a share notification signal to theclient device associated with the first A/V doorbell at block B790. Atblock B796, the network receives a playback request signal from thefirst client device. At block B798, the network transmits a video signalto the first client device.

FIG. 43 is a functional block diagram illustrating a system 800 forsharing video footage from audio/video recording and communicationdevices according to the present embodiments. The system 800 maycomprise a backend API 802 including one or more components. A backendAPI (application programming interface) may comprise, for example, aserver (e.g. a real server, or a virtual machine, or a machine runningin a cloud infrastructure as a service), or multiple servers networkedtogether, exposing at least one API to client(s) accessing it. Theseservers may include components such as application servers (e.g.software servers), depending upon what other components are included,such as a caching layer, or database layers, or other components. Abackend API may, for example, comprise many such applications, each ofwhich communicate with one another using their public APIs. In someembodiments, the API backend may hold the bulk of the user data andoffer the user management capabilities, leaving the clients to have verylimited state.

The backend API 802 illustrated FIG. 43 may include one or more APIs804. An API is a set of routines, protocols, and tools for buildingsoftware and applications. An API expresses a software component interms of its operations, inputs, outputs, and underlying types, definingfunctionalities that are independent of their respectiveimplementations, which allows definitions and implementations to varywithout compromising the interface. Advantageously, an API may provide aprogrammer with access to an application's functionality without theprogrammer needing to modify the application itself, or even understandhow the application works. An API may be for a web-based system, anoperating system, or a database system, and it provides facilities todevelop applications for that system using a given programming language.In addition to accessing databases or computer hardware like hard diskdrives or video cards, an API can ease the work of programming GUIcomponents. For example, an API can facilitate integration of newfeatures into existing applications (a so-called “plug-in API”). An APIcan also assist otherwise distinct applications with sharing data, whichcan help to integrate and enhance the functionalities of theapplications.

The backend API 802 illustrated in FIG. 43 may further include one ormore services 806, 808 (also referred to as network services). A networkservice is an application that provides data storage, manipulation,presentation, communication, and/or other capability. Network servicesare often implemented using a client-server architecture based onapplication-layer network protocols. Each service may be provided by aserver component running on one or more computers (such as a dedicatedserver computer offering multiple services) and accessed via a networkby client components running on other devices. However, the client andserver components can both be run on the same machine. Clients andservers may have a user interface, and sometimes other hardwareassociated with them.

The backend API 802 illustrated in FIG. 43 includes an alert areasservice 806. The alert areas service 806 may comprise one or more datastructures 810 storing information about a plurality of A/V recordingand communication devices. For example, the information may include thelocation of each device (such as the street address of each device), andthe size of the alert radius around each device. The alert areas service806 may access the information in the data structure(s) 810 when neededto determine which users will receive a share notification when a firstuser shares recorded video footage, as further described below. Thealert areas service 806 may also maintain the information in the datastructure(s) 810 and update the information in the data structure(s) 810when new A/V recording and communication devices are activated, whenexisting A/V recording and communication devices are deactivated, and/orwhen the alert radii around existing A/V recording and communicationdevices are changed.

In the system 800 of FIG. 43, a first A/V recording and communicationdevice 812 (A/V Doorbell 812 #1) may record video footage, which mayalso include audio. The doorbell 812 sends a first alert signal and afirst video signal 814 to the API 804, and the API 804 receives thefirst alert signal and the first video signal 814. The first videosignal includes images (the video footage) captured by a camera of thedoorbell 812. The API 804 transmits to a first client device 816 (User'sClient Device #1), in response to receiving the first alert signal andthe first video signal 814, a second alert signal and a second videosignal 818. The second alert signal may be, for example, a pushnotification. The second video signal includes the images captured bythe camera of the doorbell 812. The user associated with the firstclient device 816 may be the owner/user of the doorbell 812 (A/VDoorbell #1). The user, upon receiving the second alert signal, maychoose to answer the second alert signal, which may, for example, open alive call between the user and the visitor at the doorbell 812.Alternatively, the user may ignore the second alert signal (e.g. choosenot to answer the call). If the user ignores the second alert signal, heor she may still view the video footage of the second video signal at alater time. After viewing (or while viewing) the video footage on thedisplay of his or her client device 816, the user may decide to sharethe video footage with other users. For example, the user may tap a“share” button from within an application executing on his or her clientdevice 816. The first client device 816 then sends a share signal 820 tothe API 804, and the API 804 receives the share signal 820 from thefirst client device 816. The share signal 820 may include textdescribing the images captured by the camera of the doorbell 812 (A/VDoorbell #1). In response to receiving the share signal 820 from thefirst client device 816, the API 804 sends identifying information 822to the alert areas service 806. For example, the identifying information822 may include an identifier for the user associated with A/V Doorbell#1 and an identifier for the video footage that is to be shared withother users. Alternatively, the identifying information 822 may includean identifier for A/V Doorbell #1 (rather than an identifier for theuser associated with A/V Doorbell #1) and an identifier for the videofootage that is to be shared with other users. The alert areas service806 accesses the alert areas data structure(s) 810 and determines, basedon the identifying information 822, the other users who are to receive anotification of the shared video footage. For example, the alert areasservice 806, using the information stored in the alert areas datastructure(s) 810 may determine that A/V Doorbell #1 812 is within thealert radius defined around at least one other A/V recording andcommunication device. Once the other device(s) has/have been identified,the alert areas service 806 may transmit a share notification signal 824to a push notification service 808. The share notification signal 824may include the text describing the images captured by the camera of thedoorbell 812 (A/V Doorbell #1). The push notification service 808 maythen forward one or more push notifications 825 to a plurality ofprovider push notification services 826. The provider push notificationservices 826 are configured to send push notifications to client devicesthat run different operating systems. For example, Android devices mayreceive push notifications from an Android push notification service826, while iOS devices may receive push notifications from an iOS pushnotification service 826. Android is a mobile operating system (OS)developed by Google, based on the Linux kernel. iOS, by contrast, is amobile operating system created and developed by Apple Inc. anddistributed exclusively for Apple hardware. The provider pushnotification services 826 then send push notifications 828 to the clientdevices 830 associated with the other doorbell(s) identified by thealert areas service 806. The other user(s), upon receiving the pushnotifications 828, may choose to view the shared video footage.Alternatively, the other user(s) may ignore the push notifications 828.If the other user(s) ignores the push notifications 828, he or she maystill view the shared video footage at a later time. In either event(viewing the shared video footage right away or viewing the shared videofootage at a later time), one or more of the client devices 830 sends aplayback request signal (not shown) to the backend API 802 (and thebackend API 802 receives the playback request signal from the one ormore of the client devices 830). In response to receiving the playbackrequest signal from the one or more of the client devices 830, thebackend API 802 transmits a video signal (not shown) to the one or moreof the client devices 830. The video signal includes the shared videofootage. In certain embodiments, the alert areas service 806 may receivethe playback request signal from the one or more of the client devices830 and transmit the video signal to the one or more of the clientdevices 830. If the other user(s) opens the push notification, which maycontain a reference to the shared video footage, the other user(s)client device(s) 830 may use the API 804 to get the URL (UniformResource Locator) of the shared video footage and any other metadata (ifany) about the shared video footage so that the shared video footage canbe played back. If the other user(s) opens the shared video footage fromthe NEIGHBORHOOD ACTIVITY screen 716 (FIG. 34), a similar process mayoccur, but the reference to the shared video footage may be in theactivity feed item.

In some embodiments, an A/V recording and communication device may beginrecording video footage not in response to a visitor being detected, butrather when a user accesses the camera of the device to view live videofootage using his or her client device (e.g. “on-demand” viewing). Insuch embodiments, a process for sharing a video may include a step ofthe user accessing the camera of the device to view live video footageusing his or her client device (e.g. “on-demand” viewing), followed bythe user sharing the live video footage. For example, the user mayselect a share button from within an application executing on the user'sclient device (similar to the share button 584 described above withrespect to FIGS. 20 and 21), and a share signal may then be sent fromthe user's client device and received by the network device(s) (similarto step 548 described above with respect to FIG. 18), and a sharenotification signal may then be sent from the network device(s) andreceived by another client device(s) (similar to step 550 describedabove with respect to FIG. 18). Example embodiments of video-on-demandare described in U.S. patent application Ser. Nos. 62/267,762 and62/289,114, both of which are incorporated herein by reference in theirentireties as if fully set forth.

As described above, the present embodiments advantageously enable usersof A/V recording and communication devices to share video footage withone another. This feature can help reduce crime by increasing publicawareness of suspicious activity. Users can tailor the number andfrequency of alerts (notifications of shared videos) they receive byincreasing and decreasing the size of the alert radius around their ownA/V recording and communication device(s). Users will only receivealerts that result from videos recorded by other A/V recording andcommunication devices that are located within the alert area that theuser has set. Users may share videos as frequently or as infrequently asdesired, and users may view shared videos from other users as frequentlyor as infrequently as desired. When a user receives an alert, he or shecan choose to view the accompanying video immediately, or to ignore thealert. If the user ignores the alert, he or she can still view the videoat a later time using one or more menu screens within an applicationexecuting on the user's client device. The present embodiments thusadvantageously provide a tool that can be used to reduce crime rates andthat can be tailored by each user to meet his or her personalpreferences.

The present embodiments describe numerous ways for sharing videos,including via social media and/or social network(s). A social networkmay comprise a third-party network, such as NEXTDOOR®, FACEBOOK®,INSTAGRAM®, TWITTER®, etc. A social network may also comprise a networkmade up of users of A/V recording and communication devices, such asvideo doorbells and security cameras. For example, when a user shares avideo via the neighborhood share button 584 described above with respectto FIGS. 20, 21, 25, and 26, the video is shared with a social networkin which the members of the social network are users who have A/Vrecording and communication devices, such as video doorbells andsecurity cameras. The present embodiments are not limited to anyparticular kind or type of social network. Further, participants in thesocial network are not limited to users of A/V recording andcommunication devices of any particular kind or type.

In the present embodiments, some steps shown in one or more of thesequence diagrams and/or flowcharts may be omitted. For example, in theprocess for sharing video footage from a first A/V recording andcommunication device, such as shown in FIGS. 18 and 19, for example, thesteps of transmitting/receiving the first alert signal and the firstvideo signal and transmitting/receiving the second alert signal and thesecond video signal may be omitted. Such an embodiment might comprise,therefore, just the steps of transmitting/receiving the share signaltransmitting/receiving the share notification signal.

FIG. 44 is a functional block diagram of a client device 850 on whichthe present embodiments may be implemented according to various aspectsof the present disclosure. The user's client device 114 described withreference to FIG. 1 may include some or all of the components and/orfunctionality of the client device 850. The client device 850 maycomprise, for example, a mobile phone such as a smartphone, or acomputing device such as a tablet computer, a laptop computer, a desktopcomputer, etc.

With reference to FIG. 44, the client device 850 includes a processor852, a memory 854, a user interface 856, a communication module 858, anda dataport 860. These components are communicatively coupled together byan interconnect bus 862. The processor 852 may include any processorused in smartphones and/or portable computing devices, such as an ARMprocessor (a processor based on the RISC (reduced instruction setcomputer) architecture developed by Advanced RISC Machines (ARM)). Insome embodiments, the processor 852 may include one or more otherprocessors, such as one or more conventional microprocessors, and/or oneor more supplementary co-processors, such as math co-processors.

The memory 854 may include both operating memory, such as random accessmemory (RAM), as well as data storage, such as read-only memory (ROM),hard drives, flash memory, or any other suitable memory/storage element.The memory 854 may include removable memory elements, such as aCompactFlash card, a MultiMediaCard (MMC), and/or a Secure Digital (SD)card. In some embodiments, the memory 854 may comprise a combination ofmagnetic, optical, and/or semiconductor memory, and may include, forexample, RAM, ROM, flash drive, and/or a hard disk or drive. Theprocessor 852 and the memory 854 each may be, for example, locatedentirely within a single device, or may be connected to each other by acommunication medium, such as a USB port, a serial port cable, a coaxialcable, an Ethernet-type cable, a telephone line, a radio frequencytransceiver, or other similar wireless or wired medium or combination ofthe foregoing. For example, the processor 852 may be connected to thememory 854 via the dataport 860.

The user interface 856 may include any user interface or presentationelements suitable for a smartphone and/or a portable computing device,such as a keypad, a display screen, a touchscreen, a microphone, and aspeaker. The communication module 858 is configured to handlecommunication links between the client device 850 and other, externaldevices or receivers, and to route incoming/outgoing data appropriately.For example, inbound data from the dataport 860 may be routed throughthe communication module 858 before being directed to the processor 852,and outbound data from the processor 852 may be routed through thecommunication module 858 before being directed to the dataport 860. Thecommunication module 858 may include one or more transceiver modulescapable of transmitting and receiving data, and using, for example, oneor more protocols and/or technologies, such as GSM, UMTS (3GSM), IS-95(CDMA one), IS-2000 (CDMA 2000), LTE, FDMA, TDMA, W-CDMA, CDMA, OFDMA,Wi-Fi, WiMAX, or any other protocol and/or technology.

The dataport 860 may be any type of connector used for physicallyinterfacing with a smartphone and/or a portable computing device, suchas a mini-USB port or an IPHONE®/IPOD® 30-pin connector or LIGHTNING®connector. In other embodiments, the dataport 860 may include multiplecommunication channels for simultaneous communication with, for example,other processors, servers, and/or client terminals.

The memory 854 may store instructions for communicating with othersystems, such as a computer. The memory 854 may store, for example, aprogram (e.g., computer program code) adapted to direct the processor852 in accordance with the present embodiments. The instructions alsomay include program elements, such as an operating system. Whileexecution of sequences of instructions in the program causes theprocessor 852 to perform the process steps described herein, hard-wiredcircuitry may be used in place of, or in combination with,software/firmware instructions for implementation of the processes ofthe present embodiments. Thus, the present embodiments are not limitedto any specific combination of hardware and software.

FIG. 45 is a functional block diagram of a general-purpose computingsystem on which the present embodiments may be implemented according tovarious aspects of the present disclosure. The computer system 900 mayexecute at least some of the operations described above. The computersystem 900 may be embodied in at least one of a personal computer (alsoreferred to as a desktop computer) 900A, a portable computer (alsoreferred to as a laptop or notebook computer) 900B, and/or a server900C. A server is a computer program and/or a machine that waits forrequests from other machines or software (clients) and responds to them.A server typically processes data. The purpose of a server is to sharedata and/or hardware and/or software resources among clients. Thisarchitecture is called the client-server model. The clients may run onthe same computer or may connect to the server over a network. Examplesof computing servers include database servers, file servers, mailservers, print servers, web servers, game servers, and applicationservers. The term server may be construed broadly to include anycomputerized process that shares a resource to one or more clientprocesses.

The computer system 900 may include at least one processor 910, memory920, at least one storage device 930, and input/output (I/O) devices940. Some or all of the components 910, 920, 930, 940 may beinterconnected via a system bus 950. The processor 910 may be single- ormulti-threaded and may have one or more cores. The processor 910 mayexecute instructions, such as those stored in the memory 920 and/or inthe storage device 930. Information may be received and output using oneor more I/O devices 940.

The memory 920 may store information, and may be a computer-readablemedium, such as volatile or non-volatile memory. The storage device(s)930 may provide storage for the system 900, and may be acomputer-readable medium. In various aspects, the storage device(s) 930may be a flash memory device, a hard disk device, an optical diskdevice, a tape device, or any other type of storage device.

The I/O devices 940 may provide input/output operations for the system900. The I/O devices 940 may include a keyboard, a pointing device,and/or a microphone. The I/O devices 940 may further include a displayunit for displaying graphical user interfaces, a speaker, and/or aprinter. External data may be stored in one or more accessible externaldatabases 960.

In some embodiments, users may tag or categorize their videos whensharing them with other users, and users may set one or more preferencesfor the type(s) of videos for which they want to receive sharenotifications. For example, FIG. 46 illustrates an embodiment of agraphical user interface (GUI) 970 for setting one or more userpreferences for the type(s) of videos for which the user wants toreceive share notifications. The Neighborhood Alert Settings screen 970includes a list 972 having a plurality of categories, including, forexample, SUSPICIOUS ACTIVITY 974, BURGLARY 976, ATTEMPTED BURGLARY 978,VANDALISM 980, THEFT 982, and OTHER 984. By selecting one or more of thelisted categories, a user may limit the type(s) of videos that will beshared with that user. For example, the user may only receive sharenotifications for shared videos that fall within one or more of thecategories that the user has selected. A GUI (not shown) similar to thatshown in FIG. 46 may be provided to users during the video sharingprocess, so that the shared videos can be tagged or categorized. In someembodiments, a user may choose not to categorize a shared video. In someembodiments, a user who has set preferences for the types of videos heor she wants to be notified about may receive share notifications foruncategorized shared videos. In alternative embodiments, a user who hasset preferences for the types of videos he or she wants to be notifiedabout may not receive share notifications for uncategorized sharedvideos.

In some embodiments, users may be able to view shared videos regardlessof where their own A/V recording and communication devices are located.In still further embodiments, even users who do not even own any A/Vrecording and communication devices may be able to view shared videos.For example, shared videos may be available through a publiclyaccessible forum, such as a website. In another example, shared videosmay be accessed by users running an application on their client devices.A user sharing a video may have the option to make the shared videoavailable to the public, or to restrict the shared video to only thoseusers identified through the processes described above, such as theprocesses of FIGS. 16-19. In still further embodiments, a user may beable to view shared videos from any area the user specifies by selectinga location on a map and specifying an alert radius around the location.In still further embodiments, a user may enable “alerts around me.” Thisfeature may work in real-time to provide the user with alerts fromwithin a given radius of the user's current location. The user's currentlocation may be determined, for example, using GPS technology and theuser's mobile client device, such as a smartphone.

In some embodiments, shared videos may be accessed by law enforcementagencies. For example, a user sharing a video may have the option tomake the shared video available to law enforcement through a web portal.Law enforcement may be able to log in through the web portal to view theshared videos. For example, the web portal may include a map viewindicating the locations of all of the shared videos. The map view mayinclude selectable markers or icons corresponding to the locations ofthe shared videos. Selecting one of the icons may open a video playerand begin playback of the shared video corresponding to the selectedicon. Different law enforcement agencies, departments, or groups mayhave different logins that grant access to specific zones, such asgeographic locations that are within the jurisdiction of each agency,department, or group.

In some embodiments, users may be able to block videos from certainother users and/or from certain locations.

In some embodiments, when a user attempts to share a video, the videomay undergo a review before being shared with other users. For example,with reference to FIG. 18, when the network 542 receives the sharesignal 548, an administrator may subsequently review the video beforethe share notification signal 550 may be sent to any client devices ofother users. If the video violates any policies, the administrator mayprevent the share notification signal 550 from being sent to any clientdevices of other users. A notification, such as an e-mail, may be sentto the user who shared the video explaining that the video did notcomply with one or more policies or guidelines. The requirement foradministrator review may apply to all users, or selectively to only someusers, such as users who have attempted to share one or moreinappropriate videos. In further embodiments, an administrator may ban auser from sharing videos, such as for repeated policy violations (suchas attempting to share one or more inappropriate videos).

As described above, another aspect of the present embodiments includesthe realization that members of a neighborhood (may also be referred toas “network of users”) may benefit from the capability of locating aperson of interest, initially identified by a first user, on image datacaptured by other users. In various embodiments, a neighborhood mayinclude a grouping of members (may also be referred to as “users”)sharing information using a neighborhood platform running on each user'sclient device. For example, the neighborhood platform may include aneighborhood alert feed that allows members to post videos, photos,and/or texts to alert other members of possible suspicious activity inthe neighborhood using a share signal. In some embodiments, a first usermay share first image data that includes a person of interest committinga criminal act or acting suspiciously. In such embodiments, other users,such as a second user, may see the shared first image data in theirneighborhood feed and be asked for permission to search second imagedata captured by devices associated with the second user for a match ofthe person of interest. Further, if the person of interest is found inthe second image data, the matched second image data may be appended tothe first image data of the person of interest and further shared toother users of the network. In other embodiments, a first user may nothave video but may still share a text-based description of a person ofinterest. In such embodiments, other users, such as the second user, maysee the shared text-based description of the person of interest and beasked for permission to search the second image data for a match of thetext-based description of the person of interest. In addition, if theperson of interest is found in the second image data, the matched secondimage data may be included with the text-based description of the personof interest and further shared to other users of the network. In theseways, neighborhood safety may be enhanced by tracking movement andactivity of the person of interest and providing multiple data pointsfor users of the network to see suspicious and/or criminal patterns inthe neighborhood. The present embodiments provide these advantages andenhancements, as described below.

FIG. 47 is a functional block diagram illustrating a system 1000 forcommunicating in a network using a share signal. In various embodiments,the share signal may include image data and/or a text-based descriptionof a person of interest, as described below. For example, a first clientdevice may share first image, audio, and/or text data using a sharesignal, and the network may receive the share signal. As furtherdescribed below, the network may include one or more backend devicesthat may be configured to receive the share signal, identify one or morepersons of interest, and search second image, audio, and/or text datafrom various other users in the network for a match of the person ofinterest. In some embodiments, if a match is found, an alert signal thatincludes a notification that a person of interest was matched may besent to the user associated with the second image, audio, and/or textdata. Further, in some embodiments, if a match of the person of interestis found, the share signal may be appended to include the matched secondimage, audio, and/or text data. Thus, a person of interest identified inthe share signal may be further identified and tracked in captured datafrom other users beyond the user of the first client device, as furtherdescribed below.

In reference to FIG. 47, the system 1000 may include one or more firstaudio/video (A/V) recording and communication devices 1002 configured toaccess a first user's network 1008 to connect to a network(Internet/PSTN) 1010. The system 1000 may also include one or more firstclient devices 1004, 1006, which in various embodiments may beconfigured to be in network communication with the first A/V recordingand communication device 1002. The first client devices 1004, 1006 maycomprise, for example, a mobile phone such as a smartphone, or acomputing device such as a tablet computer, a laptop computer, a desktopcomputer, etc. The first client devices 1004, 1006 may include any orall of the components and/or functionality of the client device 114and/or the client device 850 described herein. In some embodiments, thefirst client devices 1004, 1006 may not be associated with a first A/Vrecording and communication device, as described above.

In various embodiments, the system 1000 may also include one or moresecond A/V recording and communication devices 1012 connected to thenetwork (Internet/PSTN) 1010 using a second user's network 1018 toconnect to the network (Internet/PSTN) 1010. The system 1000 may furtherinclude one or more second client devices 1014, 1016, which in variousembodiments may be configured to be in network communication with thesecond A/V recording and communication device 1012. The second clientdevices 1014, 1016 may comprise, for example, a mobile phone such as asmartphone, or a computing device such as a tablet computer, a laptopcomputer, a desktop computer, etc. The second client devices 1014, 1016may include any or all of the components and/or functionality of theclient device 114 and/or the client device 850 described herein. In someembodiments, the second client devices 1014, 1016 may not be associatedwith a second A/V recording and communication device, as describedabove.

In some embodiments, the system 1000 may also include one or more thirdparty A/V recording and communication devices 1020 connected to thenetwork (Internet/PSTN) 1010 using various third party networks 1026such as a local network, a wireless network such as a cellular/mobilenetwork and/or a Wi-Fi network, a wired network such as an Ethernetnetwork, a public network, a low-bandwidth network, and/or any otherappropriate network to access the network (Internet/PSTN) 1010. Thesystem 1000 may further include one or more third party client devices1022, 1024, which in various embodiments may be configured to be innetwork communication with the third party A/V recording andcommunication device 1020. The third party client devices 1022, 1024 maycomprise, for example, a mobile phone such as a smartphone, or acomputing device such as a tablet computer, a laptop computer, a desktopcomputer, etc. The third party client devices 1022, 1024 may include anyor all of the components and/or functionality of the client device 114and/or the client device 850 described herein. In some embodiments, thethird party client devices 1022, 1024 may not be associated with a thirdparty A/V recording and communication device, as described above.

With further reference to FIG. 47, the system 1000 may also includevarious backend devices such as (but not limited to) storage devices1032, backend servers 1030, and backend APIs 1028 in networkcommunication with the first, second, and third party A/V communicationdevices 1002, 1012, 1020 and their respective client devices 1004, 1006,1014, 1016, 1022, 1024. In some embodiments, the storage devices 1032may be a separate device from the backend servers 1030 (as illustrated)or may be an integral component of the backend servers 1030. Inaddition, the first user's network 1008 and the network 1010 may besimilar in structure and/or function to the user's network 110 and thenetwork 112 (FIG. 1), respectively. In some embodiments, the first andsecond A/V recording and communication devices 1002, 1012 may be similarin structure and/or function to the A/V doorbell 100 (FIG. 1) and/or theA/V recording and communication doorbell 130 (FIGS. 2-12). In someembodiments, the first user's client devices 1004, 1006 may be similarin structure and/or function to the user's client device 114 (FIG. 1)and/or the user's client device 850 (FIG. 44). Further, the seconduser's network 1018 may be similar in structure and/or function to theuser's network 110 (FIG. 1). In some embodiments, the second user'sclient devices 1014, 1016 may also be similar in structure and/orfunction to the user's client device 114 (FIG. 1) and/or the user'sclient device 850 (FIG. 44). Also, the storage devices 1032 may besimilar in structure and/or function to the storage device 116 (FIG. 1).In addition, in some embodiments, the backend servers 1030 and backendAPIs 1028 may be similar in structure and/or function to the server 118and the backend API 120 (FIG. 1), respectively.

In various embodiments, the first user's client devices 1004, 1006and/or the second client devices 1014, 1016 may connect to the network(Internet/PSTN) 1010 using any network, including, without limitation, alocal network, a wireless network such as a cellular/mobile networkand/or a Wi-Fi network, a wired network such as an Ethernet network, apublic network, a low-bandwidth network, and/or any other appropriatenetwork to access the network (Internet/PSTN) 1010.

FIG. 48 is a functional block diagram illustrating an embodiment of thefirst A/V recording and communication device 1002 according to variousaspects of the present disclosure. The first A/V recording andcommunication device 1002 may comprise a processing module 1050 that isoperatively connected to a camera 1040, a microphone 1042, a speaker1044, and a communication module 1046. The processing module 1050 maycomprise a processor 1052, volatile memory 1054, and non-volatile memory1056 that includes a camera application 1058. In various embodiments,the camera application 1058 may configure the processor 1052 to capturefirst image data 1060 using the camera 1040 and first audio data 1062using the microphone 1042. In some embodiments, the camera application1058 may also configure the processor 1052 to generate first text data1064 describing the first image data 1060 and/or the first audio data1062. In other embodiments, the first text data 1064 describing thefirst image data 1060 may be generated by a user using the first clientdevice 1004, 1006 associated with the first A/V recording andcommunication device 1002, as described above. In some embodiments, thefirst text data 1064 describing the first audio data 1062 may be atranscription of the first audio data 1062. In addition, the cameraapplication 1058 may configure the processor 1052 to transmit the firstimage data 1060, the first audio data 1062, and/or the text data 1064 tothe first client device 1004, 1006 using the communication module 1046,and the first client device 1004, 1006 may generate and transmit a sharesignal 1048 using the first image data 1060, the first audio data 1062,and/or the text data 1064 to the backend server 1030, as describedabove. In other embodiments, the camera application 1058 may configurethe processor 1052 to directly generate and transmit a share signal 1048using the first image data 1060, the first audio data 1062, and/or thetext data 1064 to the backend server 1030 using the communication module1046. As further described below, the backend server 1030 may identify aperson of interest in the share signal 1048 and match the person ofinterest in second image data, as further described below. In someembodiments, the backend server 1030 may also identify an object ofinterest in the share signal 1048 and match the object of interest insecond image data provided by the second A/V recording and communicationdevice 1012. Further, in some embodiments, the share signal 1048 mayonly include first text data 1064 that includes a text-based descriptionof a person and/or object of interest and the backend server 1030 mayuse the first text data 1064 to search and match the text-baseddescription in the second image data, as further described below. Inaddition, in some embodiments, the share signal 1048 may only includefirst audio data 1062 of a person and the backend server 1030 may usethe first audio data 1062 to search and match the person of interestusing the second audio data, as further described below.

FIG. 49 is a functional block diagram illustrating an embodiment of thesecond A/V recording and communication device 1012 according to variousaspects of the present disclosure. The second A/V recording andcommunication device 1012 may comprise a processing module 1080 that isoperatively connected to a camera 1070, a microphone 1072, a speaker1074, and a communication module 1076. The processing module 1080 maycomprise a processor 1082, volatile memory 1084, and non-volatile memory1086 that includes a camera application 1088. In some embodiments, thecamera application 1088 may configure the processor 1082 to capturesecond image data 1090 using the camera 1070 and second audio data 1092using the microphone 1072. In some embodiments, the camera application1088 may also configure the processor 1082 to generate second text data1094 describing the second image data 1090 and/or the second audio data1092. In other embodiments, the second text data 1094 describing thesecond image data 1090 may be generated by a user using the secondclient device 1014, 1016 associated with the second A/V recording andcommunication device 1012, as described above. In some embodiments, thesecond text data 1094 describing the second audio data 1092 may be atranscription of the second audio data 1092. In various embodiments, thecamera application 1088 may also configure the processor to generate andtransmit an output signal 1096 that may include the second image data1090, the second audio data 1092, and/or the second text data 1094. Insome embodiments, the output signal 1096 may be transmitted, using thecommunication module 1076, to the second client device 1014, 1016, andthe second client device 1014, 1016 may send the output signal 1096 tothe backend server 1030. In other embodiments, the output signal 1096may be transmitted directly to the backend server 1030 using thecommunication module 1076. In either embodiment, the backend server 1030may search the output signal 1096 to find a match of the person ofinterest identified in the share signal, as further described below. Forexample, in some embodiments, the backend server 1030 may receive firstimage data 1060 of a person of interest and may search and find a matchof the person of interest in the second image data 1090. In a furtherexample, in some embodiments, the backend server 1030 may receive atext-based 1064 description of a person of interest and may search andfind a match of the person of interest in second image data 1090. Insome embodiments, the backend server 1030 may first transmit to a secondclient device 1014, 1016 associated with the second A/V recording andcommunication device 1012, a request to check the second image data 1090for a person of interest before searching the second image data 1090, asfurther described below.

FIG. 50 is a functional block diagram illustrating one embodiment of thefirst client device(s) 1004, 1006 according to various aspects of thepresent disclosure. As described above, the first client device(s) 1004,1006 may be configured to share video footage captured by the first A/Vrecording and communication device 1002 using a share signal 1048. Thefirst client device(s) 1004, 1006 may include a processing module 1100that is operatively connected to a camera 1114 and a microphone 1116.The processing module 1100 may comprise a processor 1102, volatilememory 1104, and non-volatile memory 1106. The non-volatile memory 1106may include a client application 1108 that configures the processor 1102to capture first image data using the camera 1114 and first audio datausing the microphone 1116. The first client device(s) 1004, 1006 mayalso include a communication module 1112 for network communication withthe first A/V recording and communication device 1002 and/or the backendserver 1030. In some embodiments, the first client device(s) 1004, 1006may receive the first image data 1060 and first audio data 1062 capturedby the first A/V recording and communication device(s) 1002, asdescribed above. Further, the first client device(s) 1004, 1006 may beconfigured to receive first text data 1064 input by a first user thatdescribes the first image data 1060 and/or the first audio data 1062. Invarious embodiments, the share signal 1048 may include the first imagedata 1060, first audio data 1062, and/or the first text data 1064. Insome embodiments, the share signal 1048 may also include the first imagedata captured using the camera 1114, the first audio data captured usingthe microphone 1116 of the first client device 1004, 1006. Further, thefirst client device(s) 1004, 1006 may transmit the share signal 1048 tothe backend server 1030, where the contents of the share signal may beprovided to members of a neighborhood using client devices such as (butnot limited to) first client devices 1004, 1006 and second clientdevices 1014, 1016, as further described below.

In further reference to FIG. 50, the first client device 1004, 1006 maytransmit to the backend server 1030 the first text data 1064 thatincludes a text-based description of a person of interest, as furtherdescribed below. In some embodiments, the backend server 1030 may searchand match second image data 1090 to the text-based description, andtransmit the matched second image data 1090 and a confirmation of personrequest signal 1161 to the first client device 1004, 1006. In suchembodiments, a user of the first client device 1004, 1006 may review thematched second image data 1090 and transmit a confirmation of personacknowledgment signal 1163 to the backend server 1030 verifying that thesecond image data 1090 does include the person of interest as describedin the first text data 1064 of the text-based description of the personof interest, as further described below.

FIG. 51 is a functional block diagram illustrating one embodiment of thesecond client device(s) 1014, 1016 according to various aspects of thepresent disclosure. In many embodiments, the second client device 1014,1016 may include a processing module 1120 that is operatively connectedto a camera 1132 and a microphone 1134. The processing module 1120 maycomprise a processor 1122, volatile memory 1124, and non-volatile memory1126. The non-volatile memory 1126 may include a client application 1128that configures the processor 1122 to capture second image data usingthe camera 1132. The second client device 1014, 1016 may also include acommunication module 1130 for network communication with the second A/Vrecording and communication device 1012. For example, in someembodiments, the second client device 1014, 1016 may receive the secondimage data 1090 and the second audio data 1092 from the second A/Vrecording and communication device 1012 using the communication module1130. Further, the second client device 1014, 1016 may be configured toreceive second text data 1094 provided by a second user that describesthe second image data 1090 and/or the second audio data 1092. In someembodiments, the second client device 1014, 1016 may transmit the secondimage data 1090, second audio data 1092, and/or the second text data1094 to the backend server 1030. In other embodiments, the second A/Vrecording and communication device 1012 may directly transmit the secondimage data 1090, second audio data 1092, and/or the second text data1094 to the backend server 1030 via the output signal 1096, as describedabove.

In further reference to FIG. 51, the second client device 1014, 1016 mayreceive from the backend server 1030 the first image data 1060 thatincludes the person of interest and a second image data access requestsignal 1150 that includes a request to check the second image data 1090for the person of interest. If the second user grants permission, thenthe second client device 1014, 1016 may transmit a locate person commandsignal 1152 in response to the request to check the second image data1090 for the person of interest. If the person of interest is matched inthe second image data 1090, the second client device 1014, 1016 mayreceive an alert signal 1156 that includes a notification that theperson of interest was matched in the second image data 1090. In someembodiments, the alert signal 1156 may also include a second image datashare request signal 1164 that requests permission to share the secondimage data 1090 of the matched person of interest with the network ofusers. In other embodiments, the second image data share request signal1164 may be a separate signal from the alert signal 1156. In someembodiments, if the second user grants permission, then the secondclient device 1014, 1016 may transmit an append signal 1154 thatincludes a command to append the second image data 1090 of the matchedperson of interest onto the shared first image data 1060 of the personof interest, as further described below. In some embodiments, if thesecond user grants permission, then the second client device 1014, 1016may transmit a second image data share acknowledgment signal 1165 thatincludes a confirmation to share the matched second image data 1090 withthe first client device(s) 1004, 1006, and/or the network of users.

In reference to FIGS. 48, 49, 50, and 51, the image data 1060, 1090 maycomprise image sensor data such as (but not limited to) exposure valuesand data regarding pixel values for a particular sized grid. Further,image data may comprise converted image sensor data for standard imagefile formats such as (but not limited to) JPEG, JPEG 2000, TIFF, BMP, orPNG. In addition, image data may also comprise data related to video,where such data may include (but is not limited to) image sequences,frame rates, and the like. Moreover, image data may include data that isanalog, digital, uncompressed, compressed, and/or in vector formats.Image data may take on various forms and formats as appropriate to therequirements of a specific application in accordance with the presentembodiments. As described herein, the term “record” may also be referredto as “capture” as appropriate to the requirements of a specificapplication in accordance with the present embodiments. In addition, acommunication module, such as the communication modules 1046, 1076 maycomprise (but is not limited to) one or more transceivers and/orwireless antennas (not shown) configured to transmit and receivewireless signals. In further embodiments, the communication modules1046, 1076 may comprise (but are not limited to) one or moretransceivers configured to transmit and receive wired and/or wirelesssignals.

FIG. 52 is a functional block diagram illustrating one embodiment of abackend server 1030 according to various aspects of the presentdisclosure. The backend server 1030 may comprise a processing module1170 comprising a processor 1172, volatile memory 1174, a networkinterface 1119, and non-volatile memory 1176. The network interface 1119may allow the backend server 1030 to access and communicate with devicesconnected to the network (Internet/PSTN) 1010. The non-volatile memory1176 may include a server application 1178 that configures the processor1172 to receive the share signal 1048 and perform processes forsearching and matching for a person of interest, as further describedbelow. In various embodiments, the share signal 1048 may include firstimage data 1060, first audio data 1062, and/or text data 1068 receivedfrom the first client device 1004, 1006 and/or the first A/V recordingand communication device 1002. Further, the non-volatile memory 1176 mayinclude an output signal 1096 that includes second image data 1090,second audio data 1092, and/or second text data 1094 received from thesecond client device 1014, 1016 and/or the second A/V recording andcommunication device 1012. As further described below, in someembodiments, the backend server 1030 may receive a text-baseddescription of a person of interest. In such embodiments, the backendserver 1030 may search image data such as (but not limited to) thesecond image data 1090 for a match of the text-based description of theperson of interest. Upon a match, the backend server 1030 may transmitthe matched second image data 1090 with a confirmation of person requestsignal 1161 requesting confirmation from the first user that the matchedsecond image data 1090 includes the person of interest. The backendserver 1030 may receive a confirmation of person acknowledgment signal1163 from the first client device(s) 1004, 1006 confirming that thematched second image data 1090 includes the person of interest. Asfurther described below, in some embodiments, the backend server 1030may receive a share signal 1048 with first image data 1060 that includesa person of interest. In such embodiments, the backend server 1030 maytransmit the first image data 1060 and a second image data accessrequest signal 1150 to the second client device(s) 1014, 1016 requestingpermission to check the second image data 1090 for the person ofinterest found in the first image data 1060. If the request ispermitted, the backend server 1030 may receive a locate person commandsignal 1152, as further described below. In addition, if the person ofinterest is matched in the second image data 1090, the backend server1030 may generate and transmit an alert signal 1156 that includes anotification that the person of interest was matched in the second imagedata 1090. In some embodiments, the backend server 1030 may also send asecond image data share request signal 1164 seeking permission to sharethe matched second image data 1090. In some embodiments, the backendserver 1030 may receive an append signal 1154 from the second clientdevice(s) 1014, 1016 that includes a command to append the second imagedata 1090 onto the shared first image data 1060 of the person ofinterest, as further described below. In some embodiments, the backendserver 1030 may receive a second image data share acknowledgment signal1165 that includes a confirmation to share the matched second image data1090 with the first client device(s) 1004, 1006 and/or the network ofusers. In some embodiments, the second image data 1090, the second audiodata 1092, and/or the second text data 1094 may be separately stored atthe backend databases 1032, where the backend server 1030 may search andmatch a person of interest found in the first image data 1060, firstaudio data 1062, and/or the first text data 1064 by comparing the firstimage data 1060, the first audio data 1062, and/or the text data 1064 toinformation stored at the databases 1032, as further described below.

In further reference to FIG. 52, the non-volatile memory 1176 may alsoinclude source identifying data 1180 that may be used to identify,and/or determine locations of, the first A/V recording and communicationdevice 1002, the second A/V recording and communication device 1012,and/or the third party A/V recording and communication device 1020. Inaddition, the source identifying data 1180 may be used to identify,and/or determine locations of, the first client device(s) 1004, 1006,the second client device(s) 1014, 1016, and/or the third party device(s)1022, 1024. In some embodiments, the server application 1178 mayconfigure the processor 1172 to generate and transmit a report signal toa third party client device 1022, 1024 and/or a law enforcement agencythat includes information indicating an approximate location of wherethe first image data 1060 was captured and/or where the second imagedata 1090 was captured, as further described below.

In the illustrated embodiment of FIGS. 48-52, the various componentsincluding (but not limited to) the processing modules 1050, 1080, 1100,1120, 1170, the communication modules 1046, 1076, 1112, 1130, and thenetwork interface 1119 are represented by separate boxes. The graphicalrepresentations depicted in each of FIGS. 48-52 are, however, merelyexamples, and are not intended to indicate that any of the variouscomponents of the first A/V recording and communication device 1002, thesecond A/V recording and communication device 1012, the first clientdevice(s) 1004, 1006, the second client device(s) 1014, 1016, or thebackend server 1030 are necessarily physically separate from oneanother, although in some embodiments they might be. In otherembodiments, however, the structure and/or functionality of any or allof the components of first A/V recording and communication device 1002may be combined. In addition, in some embodiments the communicationmodule 1046 may include its own processor, volatile memory, and/ornon-volatile memory. Likewise, the structure and/or functionality of anyor all of the components of the second A/V recording and communicationdevice 1012 may be combined. In addition, in some embodiments thecommunication module 1076 may include its own processor, volatilememory, and/or non-volatile memory. In other embodiments, the structureand/or functionality of any or all of the components of first clientdevice 1004, 1006 may be combined. In addition, in some embodiments thecommunication module 1112 may include its own processor, volatilememory, and/or non-volatile memory. Likewise, the structure and/orfunctionality of any or all of the components of the second clientdevice(s) 1014, 1016 may be combined. In addition, in some embodimentsthe communication module 1130 may include its own processor, volatilememory, and/or non-volatile memory. Further, the structure and/orfunctionality of any or all of the components of the backend server1030, may be combined. In addition, in some embodiments the networkinterface 1119 may include its own processor, volatile memory, and/ornon-volatile memory.

FIG. 53 is a flowchart illustrating an embodiment of a process 1300 forsearching second image data for a match of a person of interest providedin first image data according to various aspects of the presentdisclosure. In some embodiments, a first client device(s) 1004, 1006,may transmit a share signal 1048 that includes first image data 1060 tothe backend server 1030, where the first image data 1060 may includeimages of a person of interest. In various embodiments, the first imagedata 1060 may be captured by a first A/V recording and communicationdevice 1002 or by the first client device(s) 1004, 1006, as describedabove. Further, a second A/V recording and communication 1012 and/orsecond client device(s) 1014, 1016 may capture second image data 1090and transmit the second image data 1090 to the backend server 1030. Asfurther described below, the second image data 1090 may be searched fora match of the person of interest.

In reference to FIG. 53, the process 1300 may include the backend server1030 receiving (block B1302), from a first client device 1004, 1006, ashare signal 1048 including first image data 1060 captured by a camera1040 of the first A/V recording and communication device 1002, the firstimage data including a person of interest, as described above. In someembodiments, the share signal 1048 may include first audio data 1062captured by a microphone 1042 of the first A/V recording andcommunication device 1002 associated with the first client device 1004,1006. Further, the share signal 1048 may also include first text data1064 that describes the first image data 1060 and/or the first audiodata 1062. For example, the first text data 1064 may describe that theperson of interest has committed a criminal act or is behavingsuspiciously, as depicted in the first image data 1060 and/or the firstaudio data 1062. In alternative embodiments, and as described above, theshare signal 1048 may include the first audio data 1062 and/or the firsttext data 1064 without the first image data 1060. In addition, the sharesignal may also include a command to share the first image data 1060(and/or the first audio data 1062 and/or the text data 1064) with anetwork of users. For example, the share signal 1048 may comprise aneighborhood alert that notifies other users of a possible danger posedby the person of interest.

The process 1300 may also include receiving (block B1304) second imagedata 1090 captured by a camera 1070 of the second A/V recording andcommunication device 1012, as described above. Further, in someembodiments, the backend server 1030 may receive second audio data 1092captured by a microphone 1072 of the second A/V recording andcommunication device 1012 and/or second text data 1094 that describesthe second image data 1090 and/or the second audio data 1092. In manyembodiments, the second image data 1090 may be received (block B1304)before receiving (block B1302) the share signal 1048, and stored ineither a database(s) 1032 and/or in the non-volatile memory 1176 storageof the backend server 1030 where it may be searched upon receiving theshare signal 1048. Upon receiving the share signal 1048, the process1300 may further include transmitting (block B1306) a request, to thesecond client device(s) 1014, 1016 using a second image data accessrequest signal 1150, to check the second image data 1090 for the personof interest. In some embodiments, the backend server 1030 may alsotransmit the first image data 1060 that includes the person of interestalong with the request to check the second image data for the person ofinterest. For example, one or more second users may receive on theirsecond client device(s) 1014, 1016 a video shared by a first user thatincludes a request to check second image data 1090 captured by theirrespective second A/V recording and communication device 1012. If thesecond user grants permission, then the process 1300 may includereceiving (block B1308), from the second client device(s) 1014, 1016, alocate person command signal 1152, in response to the request to checkthe second image data 1090 for the person of interest. In someembodiments, a second user may choose to grant permission for access inadvance for future share signals 1048 that may include a person ofinterest. In such embodiments, the backend server 1030 may receive anautomatic locate command signal, and in response activate a setting forautomatically identifying a further person of interest and searching thesecond image data 1090 each time a new share signal 1048 is receivedincluding the further person of interest.

In further reference to FIG. 53, the process 1300 may include searching(block B1310) the second image data 1090 for a match (block B1312) ofthe person of interest in the first image data 1060. In manyembodiments, the search (block B1310) of the second image data 1090 fora match (block B1312) of the person of interest in the first image data1060 may be automated using various imaging processing techniques and/ormachine learning processes. For example, in some embodiments, searching(block B1310) the second image data 1090 for the match (block B1312) ofthe person of interest may be performed using facial recognitionprocesses, color matching schemes, and/or using a body build score. Insome embodiments, a match (block B1312) of the person of interest in thesecond image data 1090 may be confirmed by a human operator. Inaddition, searching (block B1310) the second image data 1090 for thematch (block B1314) of the person of interest may be restricted to asubset of the second image data 1090, such as a subset of the secondimage data captured during a predetermined length of time before and/orthe capture of the first image data 1060 that includes the person ofinterest. In many embodiments, when a match (block B1312) of the personof interest is not found, the process 1300 may include continuing tosearch (block B1310) the second image data 1090. If, after continuedsearching of the second image data 1090 at block B1310, no match of theperson of interest is found, the process 1300 may return a notificationto the second client device(s) 1014, 1016, wherein the notificationindicates that no match of the person of interest was found. However,when a match (block B1312) of the person of interest is found in thesecond image data 1090, then process 1300 may include generating andtransmitting (block B1314) an alert signal 1156 to the second clientdevice(s) 1014, 1016, wherein the alert signal 1156 includes anotification that the person of interest was matched in the second imagedata 1090.

FIG. 54 is a flowchart illustrating another embodiment of a process 1350for searching second image data for a match of a person of interestprovided in first image data according to various aspects of the presentdisclosure. In many embodiments, the process 1350 may continue fromblock B1314 of process 1300, as described above with respect to FIG. 53.In some embodiments, the alert signal 1156 that is transmitted to thesecond client device(s) 1014, 1016 may include the second image data1090 of the matched person of interest. Further, the alert signal 1156may include a request for permission to share the second image data 1090of the matched person of interest with the network of users or therequest for permission to share the second image data 1090 may betransmitted to the second client device(s) 1014, 1016 using a secondimage data share request signal 1164. If permission is granted by thesecond user, the process 1350 may include receiving (block B1352) anappend signal 1154, from the second client device(s) 1014, 1016, whereinthe append signal 1154 includes a command to append the second imagedata 1090 of the matched person of interest onto the shared first imagedata 1060 of the person of interest. The process 1350 may also includetransmitting (block B1354) the first image data 1060 and the secondimage data 1090 of the matched person of interest to the network ofusers. By including the second image data 1090 of the matched person ofinterest, the person of interest captured in the first image data 1060may be tracked and his or her whereabouts and actions captured forvarious users to increase neighborhood safety.

FIG. 55 is a flowchart illustrating an embodiment of a process 1400 forsearching image data for a match of a person of interest provided in atext-based description according to various aspects of the presentdisclosure. In some embodiments, a first client device(s) 1004, 1006,may transmit a share signal 1048 that includes first text data 1064 tothe backend server 1030, where the first text data 1064 may include atext-based description of a person of interest. In various embodiments,the first text data 1064 may be provided by a first user using the firstclient device(s) 1004, 1006 that may be associated with the first A/Vrecording and communication device 1002, as described above. Further, asdescribed above, a second A/V recording and communication 1012 and/orsecond client device(s) 1014, 1016 may capture second image data 1090and transmit the second image data 1090 to the backend server 1030. Inmany embodiments, the first user may not have first image data 1060and/or first audio data 1062 of the person of interest. Thus, thetext-based description may be used to search image data captured byvarious other users for a match of the person of interest, as furtherdescribed below.

In reference to FIG. 55, the process 1400 may include receiving (blockB1402), at the backend server 1030, a text-based description (may alsobe referred to as “first text data 1064”) of a person of interest from afirst client device(s) 1004, 1006. The process 1400 may also includereceiving (block B1404), from an A/V recording and communication devicesuch as (but not limited to) the second A/V recording and communicationdevice 1012, image data such as (but not limited to) second image data1090 captured by a camera 1070 of the second A/V recording andcommunication device 1012, as described above. Further, in someembodiments, the backend server 1030 may also receive second audio data1092 captured by a microphone 1072 of the second A/V recording andcommunication device 1012 and/or second text data 1094 that describesthe second image data 1090 and/or the second audio data 1092. In manyembodiments, the second image data 1090, second audio data 1092, and/orsecond text data 1094, may be received (block B1404) before receiving(block B1402) the text-based description of the person of interest, andstored in either a database(s) 1032 and/or in the non-volatile memory1176 storage of the backend server 1030 where it may be searched uponreceiving the first text data 1064. The process 1400 may further includesearching (block B1406) the second image data 1090 for a match of thetext-based description of the person of interest. In some embodiments,the searching (block B1406) the second image data 1090 for a match ofthe text-based description of the person of interest may be performedusing natural language processing. In some embodiments, the searching(block B1406) the second image data 1090 for a match of the text-baseddescription of the person of interest may be performed by comparing atext-based description of the second image data 1090 with the receivedtext-based description of the person of interest. If a match (blockB1408) of the person of interest is not found, then the process 1400 maycontinue to search (block B1406) the second image data 1090. If, aftercontinued searching of the second image data 1090 at block B1408, nomatch of the person of interest is found, the process 1400 may return anotification to the second client device(s) 1014, 1016, wherein thenotification indicates that no match of the person of interest wasfound. However, if a match (block B1408) is found, then the process 1400may include transmitting (block B1410), from the backend server 1030 toa second client device(s) 1014, 1016, associated with the second A/Vrecording and communication device 1012, the matched second image data1090 and a request to confirm that the matched second image data 1090includes the person of interest using a confirmation of person requestsignal 1161. In some embodiments, the backed server 1030 may also sendthe text based-description along with the matched second image data 1090and the confirmation of person request signal 1161. Further, the process1400 may include receiving (block B1412) a confirmation of personacknowledgment signal 1163, from the second client device(s) 1014, 1016,confirming that the matched second image data 1090 includes the personof interest. In some embodiments, the process 1400 may includetransmitting, to the first client device(s) 1004, 1006, the matchedsecond image data 1090 and a request to confirm that the matched secondimage data 1090 includes the person of interest. In such embodiments,the process 1400 may further include receiving, from the first clientdevice(s) 1004, 1006, a confirmation that the matched second image data1090 includes the person of interest.

FIG. 56 is a flowchart illustrating another embodiment of a process 1450for searching image data for a match of a person of interest provided ina text-based description according to various aspects of the presentdisclosure. In many embodiments, the process 1450 may continue fromblock B1412 of process 1400, as described above with respect to FIG. 55.In various embodiments, the process 1450 may include transmitting (blockB1452), from the backend server 1030 to the second client device(s)1014, 1016, a second image data share request signal 1164. In someembodiments, the second image data share request signal 1164 may includea request to share the matched second image data 1090 with a first userassociated with the first client device(s) 1004, 1006 and/or a networkof users. The process 1450 may also include receiving (block B1454),from the second client device(s) 1014, 1016, a second image data shareacknowledgment signal 1165 that includes confirmation to share thematched second image data 1090 with the first client device(s) 1004,1006 and/or the network of users. In addition, the process 1450 mayinclude transmitting (block B1456) the matched second image data 1090 tothe network of users.

FIG. 57 is a sequence diagram illustrating an embodiment of anotherprocess for searching second image data 1090 for a match of a person ofinterest according to various aspects of the present disclosure. Theprocess may include a first client device(s) 1004, 1006, a second A/Vrecording and communication device 1012, a backend device such as thebackend server 1030, a second client device(s) 1014, 1016, and a networkof users. At a time T₁, the first client device 1004, 1006 may transmita share signal 1048 including first image data 1060 that includes aperson of interest, to the backend server 1030, as described above. Inaddition, at a time T₂, the second A/V recording and communicationdevice 1012 may transmit to the backend server 1030 second image data1090 captured using a camera 1070, as described above. In manyembodiments, the second A/V recording and communication device 1012 maytransmit the second image data 1090 before the first client device(s)1004, 1006 transmits the share signal 1048. In this manner, the backendserver 1030 may have second image data 1090 that has been stored and canbe searched for a match of the person of interest found in the firstimage data 1060. However, the order of timing of T₁ or T₂ isinconsequential so long as the backend server 1030 has received thesecond image data 1090 prior to searching the second image data 1090 fora match of the person of interest. In many embodiments, the backendserver may transmit a second image data access request signal 1150 tothe second client device(s) 1014, 1016 at a time T₃, as described above.If access is granted, the second client device(s) 1014, 1016, maytransmit a locate person command signal 1152 at a time T₄, in responseto receiving the second image data access request signal 1150, asdescribed above. Upon searching and finding a match of the person ofinterest in the second image data 1090, the backend server 1030 maytransmit an alert signal 1156 at a time T₅, wherein the alert signal1156 includes a notification that the person of interest was matched inthe second image data 1090. In some embodiments, the second clientdevice(s) 1014, 1016, may then transmit an append signal 1154 at a timeT₆, that includes a command to append the second image data 1090 of thematched person of interest onto the shared first image data 1060 of theperson of interest. At a time T₇, the backend server 1030, may transmitthe first and second image data 1060, 1090 of the matched person ofinterest to the network of users.

FIG. 58 is a sequence diagram illustrating an embodiment of anotherprocess for searching second image data 1090 for a match of a person ofinterest according to various aspects of the present disclosure. Theprocess may include a first client device(s) 1004, 1006, a second A/Vrecording and communication device 1012, a backend device such as thebackend server 1030, a second client device(s) 1014, 1016, and a networkof users. At a time T₁, the first client device 1004, 1006 may transmita share signal 1048 including first text data 1064 that includes atext-based description of a person of interest, to the backend server1030, as described above. In addition, at a time T₂, the second A/Vrecording and communication device 1012 may transmit to the backendserver 1030 second image data 1090 captured using a camera 1070, asdescribed above. In many embodiments, the second A/V recording andcommunication device 1012 may transmit the second image data 1090 beforethe first client device(s) 1004, 1006 transmits the share signal 1048.In this manner, the backend server 1030 may have second image data 1090that has been stored and can be searched for a match of the person ofinterest described in the first text data 1064. As described above, theorder of timing of T₁ or T₂ is inconsequential so long as the backendserver 1030 has received the second image data 1090 prior to searchingthe second image data 1090 for a match of the person of interest. Uponfinding a match of the text-based description of the person of interestin the second image data 1090, the backend server may transmit thematched second image data 1090, the text-based description of the personof interest, and a confirmation of person request signal 1161 to thesecond client device(s) 1014, 1016 at a time T₃, as described above. Ifa second user associated with the second client device(s) 1014, 1016agrees that the matched second image data 1090 appears to match thetext-based description of the person of interest, the second clientdevice(s) 1014, 1016, may transmit a confirmation of personacknowledgment signal 1163 at a time T₄, as described above. In someembodiments, the backend server 1030 may transmit a second image datashare request signal 1164 at a time T₅, to the second client device(s)1014, 1016, seeking permission to share the second image data 1090 withother users. The second user may grant permission and transmit using thesecond client device(s) 1014, 1016 a second image data shareacknowledgment signal 1165 at a time T₆. In some embodiments, uponfinding a match of the text-based description of the person of interestin the second image data 1090, the backend server 1030 may also transmitthe matched second image data 1090 and a confirmation of person requestsignal 1161 to the first client device(s) 1004, 1006 at a time T₇. If afirst user associated with the first client device(s) 1004, 1006 agreesthat the matched second image data 1090 appears to match the text-baseddescription of the person of interest, the first client device(s) 1004,1006 may transmit a confirmation of person acknowledgment signal 1163 ata time T₈, as described above. At a time T₉, the backend server 1030,may transmit the first text data 1064 and second image data 1090 of thematched person of interest to the network of users.

FIG. 59 is a functional block diagram illustrating a system forcommunicating in a network using various signals. In some embodiments,the share signals may include image data and/or a text-based descriptionof a person of interest according to various aspects of the presentdisclosure, as further described below. In some embodiments, firstclient device(s) 1004, 1006 may transmit a share signal 1048 to backenddevices that may include information about a person of interest, asdescribed above. However, in other embodiments, various other devices,such as (but not limited to) third party devices, may transmit varioussignals that may include various data including (but not limited to)image data, audio data, and/or text data to the backend devices that mayinclude information about a person of interest that may be used tosearch and match to image data stored at the backend devices such as(but not limited to) the backend server and/or the databases.

In reference to FIG. 59, the system 1200 may include one or more firstaudio/video (A/V) recording and communication devices 1202 configured toaccess a first user's network 1208 to connect to a network(Internet/PSTN) 1210. The system 1200 may also include one or more firstclient devices 1204, 1206, which in various embodiments may beconfigured to be in network communication with the first A/V recordingand communication device 1202. The first client devices 1204, 1206 maycomprise, for example, a mobile phone such as a smartphone, or acomputing device such as a tablet computer, a laptop computer, a desktopcomputer, etc. The first client devices 1204, 1206 may include any orall of the components and/or functionality of the first client devices1004, 1006, client device 114, and/or the client device 850 describedherein. In some embodiments, the first client devices 1204, 1206 may notbe associated with a first A/V recording and communication device.

In various embodiments, the system 1200 may also include one or moresecond A/V recording and communication devices 1212 connected to thenetwork (Internet/PSTN) 1210 using a second user's network 1218 toconnect to a network (Internet/PSTN) 1210. The system 1200 may furtherinclude one or more second client devices 1214, 1216, which in variousembodiments may be configured to be in network communication with thesecond A/V recording and communication device 1212. The second clientdevices 1214, 1216 may comprise, for example, a mobile phone such as asmartphone, or a computing device such as a tablet computer, a laptopcomputer, a desktop computer, etc. The second client devices 1214, 1216may include any or all of the components and/or functionality of thesecond client devices 1014, 1016, client device 114, and/or the clientdevice 850 described herein. In some embodiments, the second clientdevices 1214, 1216 may not be associated with a second A/V recording andcommunication device.

In some embodiments, the system 1200 may also include one or more thirdparty A/V recording and communication devices 1220 connected to thenetwork (Internet/PSTN) 1210 using various third party networks 1226such as a local network, a wireless network such as a cellular/mobilenetwork and/or a Wi-Fi network, a wired network such as an Ethernetnetwork, a public network, a low-bandwidth network, and/or any otherappropriate network to access the network (Internet/PSTN) 1210. Thesystem 1200 may further include one or more third party client devices1222, 1226, which in various embodiments may be configured to be innetwork communication with the third party A/V recording andcommunication device 1220. The third party client devices 1222, 1226 maycomprise, for example, a mobile phone such as a smartphone, or acomputing device such as a tablet computer, a laptop computer, a desktopcomputer, etc. The third party client devices 1222, 1226 may include anyor all of the components and/or functionality of the first clientdevices 1004, 1006, second client devices 1014, 1016, client device 114,and/or the client device 850 described herein. In some embodiments, thethird party client devices 1222, 1226 may not be associated with a thirdparty A/V recording and communication device.

With further reference to FIG. 59, the system 1200 may also include lawenforcement A/V recording and communication devices 1228, 1230 connectedto the network (Internet/PSTN) 1210 using a law enforcement network 1236such as a local network, a wireless network such as a cellular/mobilenetwork and/or a Wi-Fi network, a wired network such as an Ethernetnetwork, a public network, a low-bandwidth network, and/or any otherappropriate network to access the network (Internet/PSTN) 1210. Inaddition, the law enforcement A/V recording and communication devices1228, 1230 may be configured to capture image data, audio data, and/ortext data and be associated with law enforcement client devices 1232,1234. In the illustrated embodiment, the law enforcement A/V recordingand communication devices include a body camera 1228 and a dashboardcamera 1230, but the illustrated devices are only examples and are notlimiting.

In further reference to FIG. 59, the system 1200 may also includevarious backend devices such as (but not limited to) storage devices1242, backend servers 1240, and backend APIs 1238 in networkcommunication with the law enforcement A/V recording and communicationdevices 1228, 1230, the first and second A/V recording and communicationdevices 1202, 1212, and the third party A/V recording and communicationdevices 1220. Further, the various backend devices 1238, 1240, 1242 maybe in network communication with the law enforcement client devices1232, 1234, the first client devices 1204, 1206, the second clientdevices 1214, 1216, and the third party client devices 1222, 1224. Insome embodiments, the storage devices 1242 may be a separate device fromthe backend servers 1240 (as illustrated) or may be an integralcomponent of the backend servers 1240. In addition, the first user'snetwork 1208 and the second user's network 1218 may be similar instructure and/or function to the user's network 1008 and network 1018(FIG. 47), respectively. Further, the network 1210 may be similar instructure and/or function to the network 1010 (FIG. 47). As describedabove, the backend devices such as the backend servers 1240 may beconfigured to receive a share signal from the first client devices 1204,1206 comprising image data and/or a text-based description of a personof interest that may be used to search stored image data for a match ofthe person of interest. Further, the backend devices such as the backendservers 1240 may also be configured to receive various signals havingimage data and/or a text-based description of a person of interest fromany A/V recording and communication device, such as the third party A/Vrecording and communication device 1220 and/or the law enforcement A/Vrecording and communication devices 1228, 1230, using the processesdescribed above. In addition, the backend devices such as the backendserver 1240 may receive the various signals having image data and/or atext-based description of a person of interest from third party clientdevices 1222, 1224, and law enforcement client devices 1232, 1234. Insome embodiments, the backend devices such as the backend server 1240may receive the various signals having image data and/or a text-baseddescription of a person of interest from third party social networksthat may include any social media service or platform that usescomputer-mediated tools that allow participants to create, share, and/orexchange information in virtual communities and/or networks, such as(but not limited to) social networking websites and/or applicationsrunning on participant devices. Non-limiting examples of social networksinclude NEXTDOOR®, FACEBOOK®, INSTAGRAM®, SNAPCHAT®, TWITTER®, etc. Insome embodiments, the backend devices such as the backend server 1240may receive the various signals from third parties, such as the generalpublic, where a member of the public may transmit a signal that includesimage data and/or a text-based description of a person of interest usingtheir third party device(s) 1222, 1224, such as, but not limited to, asmartphone, where the signal transmitted by the member of the public mayinclude image data, audio data, and/or text data.

The features of the present embodiments described herein may beimplemented in digital electronic circuitry, and/or in computerhardware, firmware, software, and/or in combinations thereof. Featuresof the present embodiments may be implemented in a computer programproduct tangibly embodied in an information carrier, such as amachine-readable storage device, and/or in a propagated signal, forexecution by a programmable processor. Embodiments of the present methodsteps may be performed by a programmable processor executing a programof instructions to perform functions of the described implementations byoperating on input data and generating output.

The features of the present embodiments described herein may beimplemented in one or more computer programs that are executable on aprogrammable system including at least one programmable processorcoupled to receive data and/or instructions from, and to transmit dataand/or instructions to, a data storage system, at least one inputdevice, and at least one output device. A computer program may include aset of instructions that may be used, directly or indirectly, in acomputer to perform a certain activity or bring about a certain result.A computer program may be written in any form of programming language,including compiled or interpreted languages, and it may be deployed inany form, including as a stand-alone program or as a module, component,subroutine, or other unit suitable for use in a computing environment.

Suitable processors for the execution of a program of instructions mayinclude, for example, both general and special purpose processors,and/or the sole processor or one of multiple processors of any kind ofcomputer. Generally, a processor may receive instructions and/or datafrom a read only memory (ROM), or a random access memory (RAM), or both.Such a computer may include a processor for executing instructions andone or more memories for storing instructions and/or data.

Generally, a computer may also include, or be operatively coupled tocommunicate with, one or more mass storage devices for storing datafiles. Such devices include magnetic disks, such as internal hard disksand/or removable disks, magneto-optical disks, and/or optical disks.Storage devices suitable for tangibly embodying computer programinstructions and/or data may include all forms of non-volatile memory,including for example semiconductor memory devices, such as EPROM,EEPROM, and flash memory devices, magnetic disks such as internal harddisks and removable disks, magneto-optical disks, and CD-ROM and DVD-ROMdisks. The processor and the memory may be supplemented by, orincorporated in, one or more ASICs (application-specific integratedcircuits).

To provide for interaction with a user, the features of the presentembodiments may be implemented on a computer having a display device,such as an LCD (liquid crystal display) monitor, for displayinginformation to the user. The computer may further include a keyboard, apointing device, such as a mouse or a trackball, and/or a touchscreen bywhich the user may provide input to the computer.

The features of the present embodiments may be implemented in a computersystem that includes a back-end component, such as a data server, and/orthat includes a middleware component, such as an application server oran Internet server, and/or that includes a front-end component, such asa client computer having a graphical user interface (GUI) and/or anInternet browser, or any combination of these. The components of thesystem may be connected by any form or medium of digital datacommunication, such as a communication network. Examples ofcommunication networks may include, for example, a LAN (local areanetwork), a WAN (wide area network), and/or the computers and networksforming the Internet.

The computer system may include clients and servers. A client and servermay be remote from each other and interact through a network, such asthose described herein. The relationship of client and server may ariseby virtue of computer programs running on the respective computers andhaving a client-server relationship to each other.

The above description presents the best mode contemplated for carryingout the present embodiments, and of the manner and process of practicingthem, in such full, clear, concise, and exact terms as to enable anyperson skilled in the art to which they pertain to practice theseembodiments. The present embodiments are, however, susceptible tomodifications and alternate constructions from those discussed abovethat are fully equivalent. Consequently, the present invention is notlimited to the particular embodiments disclosed. On the contrary, thepresent invention covers all modifications and alternate constructionscoming within the spirit and scope of the present disclosure. Forexample, the steps in the processes described herein need not beperformed in the same order as they have been presented, and may beperformed in any order(s). Further, steps that have been presented asbeing performed separately may in alternative embodiments be performedconcurrently. Likewise, steps that have been presented as beingperformed concurrently may in alternative embodiments be performedseparately.

What is claimed is:
 1. A method comprising: receiving, from a firstclient device associated with a first audio/video recording andcommunication device (A/V device), and at a server in networkcommunication with the first A/V device, first image data captured by acamera of the first A/V device, the first image data representing imagesof a person of interest; receiving, from a second A/V device, and at theserver in network communication with the second A/V device, second imagedata captured by a camera of the second A/V device; transmitting, fromthe server, and to a second client device associated with the second A/Vdevice, the first image data; transmitting, from the server, and to thesecond client device, a request to check the second image data for theperson of interest; after sending the request, receiving, from thesecond client device, and at the server, a command to locate the personof interest; determining that the second image data represents images ofthe person of interest; and after determining that the second image datarepresents images of the person of interest, transmitting, to the secondclient device, notification that the second image data represents theperson of interest.
 2. The method of claim 1, further comprising sendingthe second image data to the second client device.
 3. The method ofclaim 1, further comprising sending, to the second client device, arequest for permission to share the second image data with a network ofusers.
 4. The method of claim 3, further comprising receiving, from thesecond client device, a command to append the second image data onto thefirst image data.
 5. The method of claim 4, further comprisingtransmitting, to at least a third client device associated with thenetwork of users, the first image data and the second image data.
 6. Themethod of claim 1, further comprising analyzing the second image datausing at least one of facial recognition, color matching schemes, and abody build score, wherein determining that the second image datarepresents images of the person of interest is based at least in part onanalyzing the second image data.
 7. The method of claim 1, furthercomprising receiving a confirmation that the second image datarepresents images of the person of interest.
 8. The method of claim 1,further comprising determining that a subset of the second image datacaptured during a predetermined length of time represents images of theperson of interest.
 9. The method of claim 1, further comprisingreceiving, from the second client device, and at the server, anadditional command to locate an additional person of interest when asignal is received.
 10. A method comprising: receiving, from a firstclient device, and at a server in network communication with the firstclient device, a text-based description of a person of interest;receiving, from an audio/video recording and communication device (A/Vdevice), and at the server in network communication with the A/V device,image data captured by a camera of the A/V device; determining, based atleast in part on the text-based description, that the image datarepresents images of the person of interest; transmitting, from theserver, and to a second client device associated with the A/V device,the data; transmitting, from the server, and to the second clientdevice, a request to confirm that the image data represents images ofthe person of interest; and receiving, from the second client device, aconfirmation that the image data represents images of the person ofinterest.
 11. The method of claim 10, further comprising transmitting,to the second client device, a request to share the image data with auser associated with the first client device.
 12. The method of claim11, further comprising receiving, from the second client device, and atthe server, a confirmation to share the image data with the first clientdevice.
 13. The method of claim 12, further comprising: transmitting, tothe first client device, the image data; and transmitting, to the firstclient device, a request to confirm that the image data representsimages of the person of interest.
 14. The method of claim 13, furthercomprising receiving, from the first client device, and at the server, aconfirmation that the image data represents images of the person ofinterest.
 15. The method of claim 10, further comprising transmittingthe image data to at least a third client device associated with anetwork of users.
 16. The method of claim 10, further comprisingtransmitting, to the second client device, a request to share the imagedata with a network of users.
 17. The method of claim 16, furthercomprising receiving, from the second client device, and at the server,a confirmation to share the image data with the network of users. 18.The method of claim 17, further comprising causing the image data to beshared with the network of users.
 19. The method of claim 10, whereindetermining the image data represents images of the person of interestis further based at least in part on using natural language processing.20. The method of claim 10, further comprising: comparing an additionaltext-based description of the image data with the text-based descriptionof the person of interest, wherein determining that the image datarepresents images of the person of interest is based at least in part oncomparing the additional text-based description with the text-baseddescription.
 21. A method comprising: receiving, from a server, and at asecond client device associated with a second audio/video recording andcommunication device (A/V device), first image data captured by a firstcamera of a first A/V device associated with a first client device, thefirst image data representing images of a person of interest;displaying, on a display of the second client device, at least one ofthe images of the person of interest; receiving, from the server, and atthe second client device, a request to access second image data tosearch for a match of the person of interest, wherein the second imagedata is captured using a second camera of the second A/V device;displaying, on the display of the second client device, the request toaccess the second image data to search for the match of the person ofinterest; receiving an input associated with locating the person ofinterest; transmitting, from the second client device, and to theserver, a command to locate the person of interest; and receiving, fromthe server, and at the second client device, a notification that thesecond image data represents images of the person of interest.
 22. Themethod of claim 21, further comprising receiving, from the server, andat the second client device, the second image data representing theperson of interest.
 23. The method of claim 21, further comprisingreceiving, from the server, and at the second client device, a requestfor permission to share the second image data with a network of users.24. The method of claim 23, further comprising: displaying, on thedisplay of the second client device, the request to share the secondimage data with the network of users; receiving an additional inputassociated with sharing the second image data with the network of users;and transmitting, from the second client device, and to the server, acommand to append the second image data onto the first image data. 25.The method of claim 21, further comprising: displaying, on the displayof the second client device, a request to automatically grant access tothe second image data to search for a match of a further person ofinterest; receiving an additional input associated with automaticallygranting the access; and transmitting, from the second client device,and to the server, permission to access the second image data to searchfor the match of the further person of interest.
 26. A non-transitorymachine-readable medium storing instructions executable by a processorof a client device, which when executed cause the client device to:receive, from a server, first image data captured by a first camera of afirst A/V recording and communication device (A/V device), wherein thefirst image data represents images of a person of interest; display, ona display of the client device, at least one of the images of the personof interest; receive, from the server, a request for permission toaccess second image data to search for a match of the person ofinterest, wherein the second image data is captured using a secondcamera of a second A/V device associated with the client device;display, on the display of the client device, the request to access thesecond image data to search for the match of the person of interest;receive an input associated with locating the person of interest;transmit to the server, a command to locate the person of interest; andreceive, from the server, a notification that the person of interest wasmatched in the second image data.
 27. The non-transitorymachine-readable medium of claim 26, storing further instructionsexecutable by the processor of the client device, which when executedfurther cause the client device to receive, from the server, the secondimage data representing images of the person of interest.
 28. Thenon-transitory machine-readable medium of claim 26, storing furtherinstructions executable by the processor of the client device, whichwhen executed further cause the client device to receive, from theserver, a request for permission to share the second image datarepresenting images of the person of interest with a network of users.29. The non-transitory machine-readable medium of claim 28, storingfurther instructions executable by the processor of the client device,which when executed further cause the client device to: display, on thedisplay of the client device, the request to share the second image datawith the network of users; receive an additional input associated withsharing the second image data; and transmit, to the server, a command toshare the second image data with the network of users.
 30. Thenon-transitory machine-readable medium of claim 26, storing furtherinstructions executable by the processor of the client device, whichwhen executed further cause the client device to: display, on thedisplay of the client device, a request to automatically grant access tothe second image data to search for a match of a further person ofinterest; receive an additional input associated with automaticallygranting the access; and transmit, to the server, permission to accessthe second image data to search for the match of the further person ofinterest.